A side note on pgBackRest: PGX created a fork and announced to maintain it under the name pgxbackup:

https://thebuild.com/blog/2026/05/01/pgxbackup-continuity-su...

German citizen as well.

So with a Jolla phone and Linux laptop, I am left in the cold.

> If you want something that is more like actual recursion (I.e., depth-first), Oracle has CONNECT BY which does not require the same kind of tracking. It also comes with extra features to help with cycle detection, stack depth reflection, etc.

All that is supported with CTEs as well. And both Postgres and Oracle support the SQL standard for these things.

You can't choose between breadth first/depth first using CONNECT BY in Oracle. Oracle's manual even states that CTE are more powerful than CONNECT BY

Nothing to do with plan caching, thats just talking about plan execution of parallel operations which is that thread or process based in PG?

If process based then they can send small parts of plan across processes.

Ah, didn't see the caching part.

Plans for prepared statements are cached though.

Yes if the client manually prepares the statement it will be cached for just that connection because in PG a connection is a process, but it won't survive from one connection to the next even in same process.

Other databases like MSSQL have prepared statements but they are rarely used now days since plan caching based on query text was introduced decades ago.

Only on a per-connection basis

You should look up the number of lawsuits German politicians dish out for being criticized online. Funded by the tax payer of course.

Except it does mean exactly that if you have money

Postgres does index de-duplication. So it's likely that even if you change the strings to enums, the index won't be that much smaller.

> Furthermore, why have two indexes with the same leading field (status)?

That indeed is a valid question.

Can we please stop calling it "sideloading"? It's simply "installing" software on hardware that I own, and that I should have full control over.

No relational database implements syntax highlighting. The tools you use to write and execute SQL queries implement that.

Or use a hand as a 5-bit integer, then you can count to 31 :)

It's hard to actually count using more than 4 bits/hand though. The quickest methods that require the least dexterity are those that count the knuckles (which are actually used in some counting traditions, unlike binary finger-counting).

I was going to refer to the new Jolla Phone, but then I realized that it doesn't have a headphone jack.

Furiphone lost theirs as well.