Skip site navigation (1) Skip section navigation (2)

Re: Logging conflicted queries on deadlocks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Subject: Re: Logging conflicted queries on deadlocks
Date: 2008-03-22 04:22:49
Message-ID: 20558.1206159769@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> One thing that I worried about for a little bit is that you can imagine
>> privilege-escalation scenarios.

> Perhaps we should only do this if the current user's ID is the same as the
> outermost session user's ID?

A conservative approach would be to report the query texts *only* in the
server log and never to the client --- this would need a bit of klugery
but seems doable.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: NikhilSDate: 2008-03-22 05:19:01
Subject: Re: Auto Partitioning Patch - WIP version 1
Previous:From: Tom LaneDate: 2008-03-22 04:08:51
Subject: Re: Logging conflicted queries on deadlocks

pgsql-patches by date

Next:From: NikhilSDate: 2008-03-22 05:19:01
Subject: Re: Auto Partitioning Patch - WIP version 1
Previous:From: Tom LaneDate: 2008-03-22 04:08:51
Subject: Re: Logging conflicted queries on deadlocks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group