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

On Tue, Feb 28, 2023 at 08:18:16AM +0100, Peter Eisentraut wrote: > I would also have asked for some kind of prefix that introduces the numbers. Okay. > I wonder what these numbers are useful for though? Is this a development > aid? Yes. > Can you do anything with these numbers? Yes. They im

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

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 mor

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

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?

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

Uggg^2 At Mon, 27 Feb 2023 17:53:08 +0900 (JST), Kyotaro Horiguchi wrote in > > Please tidy up the followging sentence properly and natural but in a > > moderately formal way, within the context of computer programs, and > > provide explanations for the individual changes you made. > > Plea

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

Uggg! At Mon, 27 Feb 2023 17:48:10 +0900 (JST), Kyotaro Horiguchi wrote in > At Mon, 27 Feb 2023 09:20:39 +0900, Michael Paquier > wrote in > > Hi all, > > > > While doing something I should not have done, I have been able to > > trigger latch.c with the error of $subject. Adding in the el

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

At Mon, 27 Feb 2023 09:20:39 +0900, Michael Paquier wrote in > Hi all, > > While doing something I should not have done, I have been able to > trigger latch.c with the error of $subject. Adding in the elog > generated some information about the PID owning the latch and > MyProcPid has made me

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

Hi all, While doing something I should not have done, I have been able to trigger latch.c with the error of $subject. Adding in the elog generated some information about the PID owning the latch and MyProcPid has made me understand immediately why I was wrong. Would there be any objections to ad