| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Mike Mascari <mascarm(at)mascari(dot)com>, 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-27 15:05:20 |
| Message-ID: | 28020.1056726320@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Joe Conway writes:
>> 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()?
> The current statement can be examined using the statistics views and
> functions.
That's not very reliable though --- unless the current query has been
running for quite a few milliseconds, there's no guarantee it will be
reflected in the statistics collector's output.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | FTL Africa | 2003-06-27 15:07:53 | PSQL NEWBIE - RUNTIME ERROR |
| Previous Message | Bruno Wolff III | 2003-06-27 14:43:34 | Re: adding fields to a table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2003-06-27 15:39:21 | Re: CODE SUBMISSION FOR NEXT RELEASE |
| Previous Message | Peter Eisentraut | 2003-06-27 14:57:07 | Re: Two weeks to feature freeze |