Re: [HACKERS] [sqlsmith] Crash reading pg_stat_activity

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: [HACKERS] [sqlsmith] Crash reading pg_stat_activity
Дата
Msg-id CAEepm=0K9uPA8WZT_FACWmRNA9qfPxhm3o+sEF10mug9KcJxZQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] [sqlsmith] Crash reading pg_stat_activity  (Thomas Munro <thomas.munro@enterprisedb.com>)
Ответы Re: [HACKERS] [sqlsmith] Crash reading pg_stat_activity  (Andreas Seltenreich <seltenreich@gmx.de>)
Re: [HACKERS] [sqlsmith] Crash reading pg_stat_activity  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Wed, Dec 28, 2016 at 11:57 AM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> But I'm starting to think that the best way might be to do BOTH of the
> things I said in my previous message: make dsa.c register on
> create/attach and also unregister before detaching iff the name was
> supplied at creation time for the benefit of extension writers, but
> make it not do anything at all about tranche name
> registration/unregistration if NULL was passed in at create time.
> Then register this particular tranche (LWTRANCHE_PARALLEL_QUERY_DSA)
> in every process in RegisterLWLockTranches.  That way, you'd get a
> useful name in pg_stat_activity for other backends that are running
> parallel queries if they are ever waiting for these locks (unlikely
> but interesting to know abotu if it happens).

Maybe something like the attached.

-- 
Thomas Munro
http://www.enterprisedb.com

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: [HACKERS] Faster methods for getting SPI results
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] ICU integration