Re: track_activity_query_size max practical size? - Mailing list pgsql-general

From Ron
Subject Re: track_activity_query_size max practical size?
Date
Msg-id 16c2a469-802c-d21c-a200-fd2516af77dd@gmail.com
Whole thread Raw
In response to Re: track_activity_query_size max practical size?  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On 7/7/23 09:51, Adrian Klaver wrote:
> On 7/7/23 07:42, Ron wrote:
>> We've got some Very Large Queries that take a long time. 
>
> An EXPLAIN(ANALYZE BUFFERS) would go a long way here.

You can't run EXPLAIN(ANALYZE BUFFERS) if you don't have a query to run.  
That's what track_activity_query_size is for.

>
>> Even setting taqs to 10KB isn't adequate, so I want to significantly bump 
>> it, but am
>
> It is before coffee here, so you will need to spell out what taqs is?

track_activity_query_size

>
>> concerned about side effects of setting it to 48KB or even 64KB.
>>
>

-- 
Born in Arizona, moved to Babylonia.



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: track_activity_query_size max practical size?
Next
From: Ron
Date:
Subject: Re: track_activity_query_size max practical size?