Re: Increasing the length of pg_stat_activity.current_query... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Increasing the length of pg_stat_activity.current_query...
Date
Msg-id 17641.1099782881@sss.pgh.pa.us
Whole thread Raw
In response to Re: Increasing the length of  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Increasing the length of pg_stat_activity.current_query...  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> Not having the whole query is painful. Raising it to 1K doesn't get
> round the fact that it's the longer queries that tend to be the more
> painful ones, and so they are the ones you want to trap in full and
> EXPLAIN, so you can find out if they are *ever* coming back. 

... so look in the postmaster log ...

> I'd vote in favour of relaxing the limit entirely, as Sean suggests.

The choice is not between "limit" and "no limit", it is between
"limit" and "broken".
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: relative_path() seems overly complicated and buggy
Next
From: Tom Lane
Date:
Subject: Re: Proposal for Recover mode in pg_ctl (in 8.0)