From: | Larry Rosenman <ler(at)lerctr(dot)org> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com>, Mike Mascari <mascarm(at)mascari(dot)com> |
Cc: | Guillaume LELARGE <gleu(at)wanadoo(dot)fr>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>, Andrew Gould <andrewgould(at)yahoo(dot)com> |
Subject: | Re: [GENERAL] capturing and storing query statement with |
Date: | 2003-06-24 21:13:31 |
Message-ID: | 60000000.1056489211@lerlaptop.iadfw.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
--On Tuesday, June 24, 2003 14:07:23 -0700 Joe Conway <mail(at)joeconway(dot)com>
wrote:
> (moving to HACKERS)
>
> Mike Mascari wrote:
>> Joe Conway wrote:
>>> I think this shows how to do what you want:
>>> http://archives.postgresql.org/pgsql-sql/2003-05/msg00301.php
>>
>> Maybe debug_query_string should be mapped into a variable like
>> CURRENT_USER? Perhaps something like CURRENT_QUERY?
>>
>
> I was thinking something similar. This exact question has come up at
> least three times in the last three months. I doubt we'd want a special
> keyword like CURRENT_QUERY, but maybe current_query()?
>
> Comments?
I was thinking the same thing. Currently I use the contrib/dblink supplied
function, but a firstclass, in the default install, version would be nice.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
From | Date | Subject | |
---|---|---|---|
Next Message | Joern Muehlencord | 2003-06-24 21:18:20 | server layout |
Previous Message | Joe Conway | 2003-06-24 21:07:23 | Re: [GENERAL] capturing and storing query statement with rules |
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Benoit | 2003-06-24 21:27:29 | Re: capturing and storing query statement with rules |
Previous Message | Bruce Momjian | 2003-06-24 21:12:18 | Re: Two weeks to feature freeze |