Re: Notice lock waits

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Notice lock waits
Date: 2016-08-05 19:17:28
Message-ID: 17899.1470424648@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> I have it PGC_SUSET because it does send some tiny amount of
> information about the blocking process (the PID) to the blocked
> process. That is probably too paranoid, because the PID can be seen
> by anyone in the pg_locks table anyway.

Why not just leave out the PID? I think it's often far too simplistic
to blame a lock wait on a single other process, anyway.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-08-05 19:26:15 Re: Heap WARM Tuples - Design Draft
Previous Message Julien Rouhaud 2016-08-05 18:53:29 Re: Notice lock waits