Re: How to get cursor query

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Mikhail <bemewe(at)mail(dot)ru>, pgsql-general(at)postgresql(dot)org
Subject: Re: How to get cursor query
Date: 2015-08-18 14:11:27
Message-ID: 8450.1439907087@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 08/18/2015 06:44 AM, Tom Lane wrote:
>> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>>> The only thing I can think to do is load pg_stat_statements:
>>> http://www.postgresql.org/docs/9.4/interactive/pgstatstatements.html

>> That won't help after-the-fact either.

> Well at some point the query will leave the view, but by default
> pg_stat_statements tracks the last 5000 distinct statements, so you have
> some time > 0 to find it.

No, you don't have any time to find it, because pg_stat_statements can
only track operations in backends that it's already been loaded into.
What's more, it requires shared memory that can only be allocated at
postmaster start, so that there's really no way to load it without a
postmaster restart.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-08-18 14:25:28 Re: How to get cursor query
Previous Message Adrian Klaver 2015-08-18 14:05:38 Re: How to get cursor query