| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |
| Date: | 2016-02-12 23:22:32 |
| Message-ID: | 20160212232232.GA29473@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-02-12 23:44:14 | Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |
| Previous Message | Bruce Momjian | 2016-02-12 22:53:41 | pgsql: pg_upgrade: Add C comment about NextXID delimiter |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-12 23:33:35 | Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions) |
| Previous Message | Bruce Momjian | 2016-02-12 22:54:11 | Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions) |