| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jonathan Ellis <jbe(at)familyellis(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: detecting deadlocks |
| Date: | 2002-01-23 02:22:53 |
| Message-ID: | 20020123132253.A29319@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 22, 2002 at 07:25:02PM -0500, Tom Lane wrote:
> SQL from other backends isn't readily available, and showing it would
> create security issues anyway (eg, could expose sensitive data values
> to someone who doesn't have the right to see 'em). About the only thing
> that we could provide given the current shared-memory datastructures is
> the PID of each backend involved in the deadlock cycle. This'd be
> somewhat useful, I guess, but not really a direct indicator of which
> command was being executed.
If the SQL queries are being logged, then the PID would be enough to find
the query in the logfile. Come to think of it though, if the deadlock
message is logged, then it would include the PID anyway...
--
Martijn van Oosterhout <kleptog(at)svana(dot)org>
http://svana.org/kleptog/
> Terrorists can only take my life. Only my government can take my freedom.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nic Ferrier | 2002-01-23 02:27:49 | Re: implemention of calls to stored procs. |
| Previous Message | Doug McNaught | 2002-01-23 02:01:38 | Re: implemention of calls to stored procs. |