Re: track_activity_query_size max practical size?

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: track_activity_query_size max practical size?
Date: 2023-07-07 14:56:19
Message-ID: 16c2a469-802c-d21c-a200-fd2516af77dd@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2023-07-07 14:58:15 Re: track_activity_query_size max practical size?
Previous Message Adrian Klaver 2023-07-07 14:55:00 Re: track_activity_query_size max practical size?