In September 2021, a patch for the upcoming PostgreSQL version 15 was committed which introduces a visible change for users: the CREATE privilege for the public schema is no longer set by default. This is a recommendation from CVE-2018-1058.
What does that mean for the average (non-superuser) user?
Jens Kubieziel recently posted a Twitter poll: 2 + 2 * 4
The available options:
Notably absent is the correct result (at least for our ordinary mathematics). This poll is a No-Win Situation: you can’t win, because the correct result is not available as an option.
Nevertheless I had an idea, but for this I had to wait until the poll closes.
The one thing I like to do is challenge PostgreSQL - and readers - to the extreme. A while ago I posted about the Beer o’clock. Building Zoé was another interesting example. And at some point I blog about Dancing with the Stars as well. Today it’s all about nothing. Empty. Where is all the data gone?
A while ago I posted this screenshot on Twitter, and as far as I can tell no one found the correct answer.
A couple days ago Devrim forked PostgreSQL to get a beer.
That effort is of course laudable, but a bit extreme.
PostgreSQL is very extensible, and allows to implement a beer now clock with just a few easy steps.
Christophe Pettus posted an interesting challenge here. Two strings which on the surface look equal, but if you ask PostgreSQL to compare them, they are not equal.
Now let me start with a note: Twitter totally screws this challenge up.
How so? Although the two strings are different in the original, when posting this to Twitter the strings are made equal. Where is the fun in that?