Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c
Дата
Msg-id Y/1D2q7YD5GxasCt@paquier.xyz
обсуждение исходный текст
Ответ на Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Список pgsql-hackers
On Mon, Feb 27, 2023 at 05:48:10PM +0900, Kyotaro Horiguchi wrote:
> +1 for adding that information, I'm afraid that MyProcId is not
> necessary since it is displayed in log lines in most cases.  If you
> want to display the both PIDs I suggest making them more distinctive.

What would you suggest?  This message is basically impossible to
reach so the wording of the patch was OK for me (see async.c) so you
would need to look at the internals anyway.  Now if you'd like
something like "could not blah: owner PID=%d, MyProcPid=%d", that's
also fine by me.
--
Michael

Вложения

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

Предыдущее
От: Vik Fearing
Дата:
Сообщение: Re: Adding argument names to aggregate functions
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: verbose mode for pg_input_error_message?