PostgreSQL 16 Beta 1

Post by Tostino » Tue, May 30, 2023, 3:34 PM UTC

dingledork69 wrote: post #29

Nextgrid wrote: post #22

Earlier quoted context omitted.

Out of curiosity, if the problem of connections being expensive is solvable by PGBouncer-style connection multiplexing, why doesn't Postgres just do that by itself?

Because pgbouncer's transaction-based pooling, which is what the previous poster was referring to, breaks a few postgres features. This is fine for most applications, but not all. See the table on https://www.pgbouncer.org/features.html

I really wish there was a way to handle transaction pooling without losing session pooling features.

Essentially, a "please serialize everything (temp tables, SET GUC values, etc) from this session to disk and load it back when necessary".

Post by Tostino » Tue, May 30, 2023, 3:37 PM UTC

paulddraper wrote: post #38

seanhunter wrote: post #30

Earlier quoted context omitted.

> - Subqueries in the FROM clause can omit aliases This is great. It never made any sense to me that this was required. For people who are unaware, say you want to understand a table a natural way of doing it might be select * from the_table order by some_metric desc limit 10 so you'd think you can do the same for queries like select * from ( select blah blah blah the rest of the query ) a order by some_metric desc l…

It never made sense. And FYI this comes from ANSI SQL.

It does the second you want to join to the results of that subquery...this is an optimization that recognizes that the alias is never used and thus can be omitted. Nice QOL feature.

Re: PostgreSQL 16 Beta 1

Re: PostgreSQL 16 Beta 1