Discussion : Savepoints and the aborted-transaction state in PostgreSQL

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

The cost of 'every statement in a savepoint' has a known cliff worth naming: each backend caches at most 64 subtransaction IDs (`PGPROC_MAX_CACHED_SUBXIDS`), and once a transaction has more than that, every other session that takes a snapshot has to consult the `pg_subtrans` SLRU instead of the cache, which is commonly reported as a sharp performance drop on busy servers. So a batch that wraps each of ten thousand rows in a savepoint hurts every concurrent transaction, not only itself. For interactive work, psql has this behaviour built in and switchable: `\set ON_ERROR_ROLLBACK interactive` makes psql issue a savepoint before each statement so that a typo does not abort the block, and the value `on` does the same for scripts.