Re: recent deadlock regression test failures
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Kevin Grittner <kgrittn@gmail.com>, Andres Freund <andres@anarazel.de>,
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-04-10T04:19:38Z
Lists: pgsql-hackers
Thomas Munro <thomas.munro@enterprisedb.com> writes: > Here's a pair of draft patches for review: I'll look at these in detail tomorrow, but: > 2. pg-safe-snapshot-blocking-pids.patch, to provide an end-user > function wrapping GetSafeSnapshotBlockingPids(). Kevin expressed an > interest in that functionality, and it does seem useful: for example, > someone might use it to investigate which backends are holding up > pg_dump --serializable-deferrrable. This is a separate patch because > you might consider it material for the next cycle, though at least > it's handy for verifying that GetSafeSnapshotBlockingPids() is working > correctly. Personally I have no problem with adding this now, even though it could be seen as a new feature. Does anyone want to lobby against? regards, tom lane
Commits
-
Move isolationtester's is-blocked query into C code for speed.
- 511540dadf11 10.0 landed