hans_castorp

Typically no.

In most (all?) cases the pooler manages one pool per database user, so even if there was something leaking, it would not be anything that the database user couldn't access anyway.

But if you are paranoid, you can configure the pooler to run "RESET ALL", "RESET ROLE", "RESET SESSION AUTHORIZATION" and "ROLLBACK" before handing out a connection.

Their license only disallows publishing the result of a benchmark

But you were always allowed to run your own benchmarks internally.

Back then, you could have installed 10gR1 and 10gR2 and compare the sort performance on identical data sets and queries.

Maps and satnav require a web connection.

No they don't require a network at all. The only drawback if there is no network is that the initial finding of the position takes longer. And maps can be downloaded so that they are available offline.

GPS receiver have been working without a "web connection" for ages (e.g. Garmins outdoor devices).

I use my smartphone in "airplane" mode but GPS enabled when hiking. No problems whatsoever.

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

Ah, didn't see the caching part.

Plans for prepared statements are cached though.

and it has no way to serialize a query plan to some form that can be shared between processes

https://www.postgresql.org/docs/current/parallel-query.html

"PostgreSQL can devise query plans that can leverage multiple CPUs in order to answer queries faster."

This is simply not true.

Some people are investigated because they spread lies, insults and threats. Things that would be investigated (and punished) as well, if done "off line".

The freedom of speech does not mean "freedom to harass, threat or insult people".

The oppression of free speech seems to be happening much more in the USA, where you are not allowed to criticize the politics of the ruling party any more.

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 :)

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

It does if you look into the README for Firefox

https://github.com/corbindavenport/just-the-browser/tree/mai...

Graphene only runs on Pixel phones

So what's his "Drill, baby, drill" about? He thinks renewable energy is the something sent by the anti-christ. The only energy source he accepts is burning fossil fuels or nuclear power.

The convicted felon in the White House doesn't give a shit about drug criminals - he just pardoned one. He is after Venezuela's oil.

Would be cool if that could be integrated into Postgres :)

With the latest Postgres version (>= 18) you do NOT need a plugin

I have seen a lot of people sort by (generated) integer values to return the rows "in creation order" assuming that sorting by an integer is somehow magically faster than sorting by a proper timestamp value (which give a more robust "creation order" sorting than a generated integer value).

For those that can read German, here is a little article that explains some of the obstacles over time:

https://www.derstandard.at/story/3000000299789/traum-vom-sue...

I don't have any "social media" accounts. I guess they won't believe me, and would deny me a visa based on the assumption that I am lying.

The German Wikipedia page[1] about the Z1 also contains a quote from Kurt Pannke, who Zuse told about his plans for the computer.

"Oh, Mr Zuse, there is absolutely nothing left to invent in the field of calculating machines. But you are a nice young engineer, I'll give you 1,500 Reichsmarks and when you have come up with something, show it to me." (Translated by Deepl)

I like the "640K ought to be enough" vibe of that statement :)

[1] https://de.wikipedia.org/wiki/Z1_(Rechner)#:~:text=Ach%2C%20...

Direct I/O is being worked on, but is not yet available.

See e.g. here: https://www.cybertec-postgresql.com/en/postgresql-18-and-bey...

Hmm, works for me (but maybe that's my uBlock or PrivacyBadger)

You need a / at the end of the URL

https://www.mjt.me.uk/posts/falsehoods-programmers-believe-a...

Don't they break up kidney stones using ultrasound as well? Or is that a different type of "ultrasound"?

I did not explicitly evict the Postgres buffer cache, but using pg_buffercache to evict all buffers for the table, yields a runtime of 23ms for me (still going for the BitmapOr).

https://notebin.de/?ac3fcf55e6850f47#ERXndRrqp3X4zEWX5EC3dZU...

Which plan does Postgres choose in your case that results 100ms?

Not sure on which Postgres version this was tested with, but the first example runs in about 2ms with my Postgres 17 installation ("cold cache"). It uses a BitmapOr on the two defined indexes.

https://notebin.de/?5ff1d00b292e1cd5#AU4Gg8hnY6RAmS9LoZ18xWn...

This used the setup.sql from the linked GitHub repository.