PostgreSQL hacker. Irish expat. A theoretician's practitioner.

San Francisco, CA
Joined June 2011
Peter Geoghegan retweeted
Insert Benchmark results for MyRocks, InnoDB and Postgres. Postgres is still boring, as it was for sysbench. I did not find serious regressions. With one exception, version 13.1 was faster & more efficient than 11.10. The exception was for loads with secondary index maintenance.
2
3
19
Show this thread
PSA: If you're ever involved in a Postgres XID wraparound related emergency, consider using VACUUM's INDEX_CLEANUP option (or the vacuum_index_cleanup table param) - that way VACUUM just does freezing stuff. VACUUM is *much* faster when run this way. Could easily save the day.
1
8
46
I committed bottom-up index deletion today, which is slated for Postgres 14. See postgresql.org/docs/devel/bt… for a detailed description. In short: it makes index bloat/VACUUM issues much less likely to get out of hand. Updaters are now *required* to clean up indexes after themselves.
5
30
89
Peter Geoghegan retweeted
For Postgres and MySQL with in-memory, low-concurrency sysbench on a small server: * Old MySQL (5.6) is faster than old Postgres (11.10) * New MySQL (8.0.21) is slower than new Postgres (13.1) * New CPU overhead is the problem. smalldatum.blogspot.com/2021…
0
12
39
Peter Geoghegan retweeted
Postgres is boring! No regressions from 11.10 to 13.1 for in-memory & low-concurrency sysbench on a small server smalldatum.blogspot.com/2021…
4
16
73
Over 5 years ago my then-colleague @brandur wrote about problems with Postgres queues and the accumulation of garbage MVCC versions (see brandur.org/postgres-queues). Expect significant improvements in this area for Postgres 14: postgr.es/m/CAGnEbogATZS1mWM…
6
15
59
Peter Geoghegan retweeted
Robert Haas (@robertmhaas): CVE-2019-9193 postgr.es/p/4ZM
0
13
8