Previously Alex Ezell wrote:
>
> Sorry the double and top post, but please disregard. I've been
> informed by a coworker that this is a PostgreSQL limitation on the
> length of the current_query column and that thus far, the PostgreSQL
> devs will not change it.
Postgres has a log_statement conf
Alex Ezell wrote:
>
>
>
> On Mar 4, 10:01 am, "Michael Bayer" wrote:
>> Alex Ezell wrote:
>>
>> > We often do diagnostics on our PostgreSQL systems by looking at
>> > currently running queries with some sql like this:
>>
>> > select procpid, to_char((now() - query_start), 'HH24:MI:SS.MS') as
>> >
On Mar 4, 10:01 am, "Michael Bayer" wrote:
> Alex Ezell wrote:
>
> > We often do diagnostics on our PostgreSQL systems by looking at
> > currently running queries with some sql like this:
>
> > select procpid, to_char((now() - query_start), 'HH24:MI:SS.MS') as
> > query_time, client_addr as cli
Sorry the double and top post, but please disregard. I've been
informed by a coworker that this is a PostgreSQL limitation on the
length of the current_query column and that thus far, the PostgreSQL
devs will not change it.
Sorry for the trouble.
/alex
On Mar 4, 9:56 am, Alex Ezell wrote:
> We
Alex Ezell wrote:
>
> We often do diagnostics on our PostgreSQL systems by looking at
> currently running queries with some sql like this:
>
> select procpid, to_char((now() - query_start), 'HH24:MI:SS.MS') as
> query_time, client_addr as client_host, current_query
> from pg_stat_activity
> where
