| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | 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 rules |
| Date: | 2003-06-24 21:07:23 |
| Message-ID: | 3EF8BD8B.9040401@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
(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?
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-06-24 21:13:31 | Re: [GENERAL] capturing and storing query statement with |
| Previous Message | Mike Mascari | 2003-06-24 21:05:25 | Re: capturing and storing query statement with rules |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-06-24 21:12:11 | Re: interval's and printing... |
| Previous Message | Mike Mascari | 2003-06-24 21:05:25 | Re: capturing and storing query statement with rules |