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

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c
Дата
Msg-id 74730711-4ccb-09e4-8450-8edf14020767@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Provide PID data for "cannot wait on a latch owned by another process" in latch.c  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On 28.02.23 00:59, Michael Paquier wrote:
> 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.

I would also have asked for some kind of prefix that introduces the numbers.

I wonder what these numbers are useful for though?  Is this a 
development aid?  Can you do anything with these numbers?



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

Предыдущее
От: John Naylor
Дата:
Сообщение: Re: [PoC] Improve dead tuple storage for lazy vacuum
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Allow tests to pass in OpenSSL FIPS mode