Re: Improving connection scalability: GetSnapshotData()

David Steele <david@pgmasters.net>

From: David Steele <david@pgmasters.net>
To: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2020-03-04T14:04:08Z
Lists: pgsql-hackers
On 3/1/20 3:36 AM, Andres Freund wrote:
> 
> I think these are pretty nice results.

Indeed they are.

Is the target version PG13 or PG14?  It seems like a pretty big patch to 
go in the last commitfest for PG13.

Regards,
-- 
-David
david@pgmasters.net



Commits

  1. Try to unbreak 021_row_visibility.pl on mingw.

  2. Fix and test snapshot behavior on standby.

  3. Fix race condition in snapshot caching when 2PC is used.

  4. snapshot scalability: cache snapshots using a xact completion counter.

  5. Fix use of wrong index in ComputeXidHorizons().

  6. Make vacuum a bit more verbose to debug BF failure.

  7. snapshot scalability: Introduce dense array of in-progress xids.

  8. snapshot scalability: Move PGXACT->vacuumFlags to ProcGlobal->vacuumFlags.

  9. snapshot scalability: Move subxact info to ProcGlobal, remove PGXACT.

  10. snapshot scalability: Move PGXACT->xmin back to PGPROC.

  11. snapshot scalability: Don't compute global horizons while building snapshots.

  12. BRIN: Handle concurrent desummarization properly

  13. Track latest completed xid as a FullTransactionId.

  14. Rename VariableCacheData.nextFullXid to nextXid.

  15. snapshot scalability: Move delayChkpt from PGXACT to PGPROC.

  16. Report progress of CREATE INDEX operations