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

From Adrian Klaver
Subject Re: track_activity_query_size max practical size?
Date
Msg-id 1cf118ea-91da-d9bf-2ed9-c079e2653964@aklaver.com
Whole thread Raw
In response to Re: track_activity_query_size max practical size?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: track_activity_query_size max practical size?
List pgsql-general
On 7/7/23 07: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.
> 
>> 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?

Did I mention lack of coffee? I see  track_activity_query_size in the 
subject. So the issue is what with the current setting?

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

-- 
Adrian Klaver
adrian.klaver@aklaver.com




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?