Postgres 17 Commit-orama | Scaling Postgres 312

To get the show notes as well as get notified of new episodes, visit:
www.scalingpostgres.com/episo...
In this episode of Scaling Postgres, we cover potential features in Postgres 17 such as explain serialize, verbose copy, pg_buffer_cache_evict, as well as many others.
Timestamps:
00:00 - Intro
00:28 - Waiting for PostgreSQL17: Invent SERIALIZE option
02:17 - Waiting for PostgreSQL17: Add new COPY option LOG_VERBOSITY
03:50 - PostgreSQL17: pg_buffercache_evict()
04:45 - Waiting for PostgreSQL17: Benchmarking with pg_ buffercache_evict
06:00 - PostgreSQL 17 features I am most waiting for
06:23 - A look at the Elephants Truck PostgreSQL 17
08:29 - Waiting for PostgreSQL17: Add support for MERGE... WHEN NOT MATCHED BY SOURCE
09:34 - PostgreSQL17 commitfest conclusion
10:08 - Logical replication common issues
11:13 - GQL: 2024 is out
11:39 - A New Approach to Database Development
12:29 - Outro
#postgres #postgresq

[@professortrog7742]

Uhm, in that 'Simple' example of the explain serialize, the output that should be sent to the client is 28GB (!!) That is just.... silly.

[@jaimeduncan6167]

More or less, in my company, 28GB of data is not unheard of. It's every single day we have a bunch of queries returning more than 28GB some by a factor of 10 to 20 during the moring hours from 7 to 11, and multiple times to different computers in the application cluster. It's just the nature of our business.