Re: track_activity_query_size note - Mailing list pgsql-docs

From Magnus Hagander
Subject Re: track_activity_query_size note
Date
Msg-id CABUevExX5i111ceG+9jmYwdbOd_Az3K6vw7wq+-4R6A=1XygeA@mail.gmail.com
Whole thread Raw
In response to Re: track_activity_query_size note  (Thom Brown <thom@linux.com>)
Responses Re: track_activity_query_size note  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On Thu, May 24, 2012 at 2:59 PM, Thom Brown <thom@linux.com> wrote:
> On 24 May 2012 13:54, Magnus Hagander <magnus@hagander.net> wrote:
>> On Thu, May 24, 2012 at 2:49 PM, Thom Brown <thom@linux.com> wrote:
>>> On 24 May 2012 13:39, Magnus Hagander <magnus@hagander.net> wrote:
>>>> On Thu, May 24, 2012 at 2:16 PM, Thom Brown <thom@linux.com> wrote:
>>>>> Hi,
>>>>>
>>>>> I attach a proposed change to the docs which points out that if the
>>>>> size of track_activity_query_size is changed and the is server
>>>>> restarted, it won't have any effect if query statistics are already
>>>>> present.
>>>>
>>>> But aren't pg_stat_activity queries always cleared when you restart
>>>> the server - because they are all disconnected... And you can't change
>>>> track_activity_query_size without restarting.
>>>
>>> But not pg_stat_statistics queries, which is where I should have
>>> probably made the note.  Restarting the server won't change the length
>>> of the field if there's already data present in pg_stat_statistics,
>>> but upon resetting them, the field is appropriately sized.
>>
>> Uh, what's pg_stat_statistics?
>
> s/pg_stat_statistics/pg_stat_statements/

Ah, suddenly it makes sense.

And in that case yes, the docs changes should go under
pg_stat_statements, I believe.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-docs by date:

Previous
From: Thom Brown
Date:
Subject: Re: track_activity_query_size note
Next
From: Tom Lane
Date:
Subject: Re: track_activity_query_size note