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

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Дата
Msg-id 20160212232232.GA29473@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.  (Robert Haas <robertmhaas@gmail.com>)
Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)