Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Date
Msg-id 20160212232232.GA29473@awork2.anarazel.de
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
List pgsql-hackers
On 2016-02-12 13:16:54 -0500, Tom Lane wrote:
> Investigation showed that there are a couple of reasons.  One,
> isolationtester's is-it-waiting query takes an insane amount of
> time under CLOBBER_CACHE_ALWAYS --- over half a second on my
> reasonably new server.

I wonder if we shouldn't just expose a 'which pid is process X waiting
for' API, implemented serverside. That's generally really useful, and
looks like it's actually going to be less complicated than that
query... And it's surely going to be faster.

Andres



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)
Next
From: Michael Paquier
Date:
Subject: Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)