From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: track_activity_query_size max practical size?
Date: Fri, 7 Jul 2023 09:56:19 -0500
Message-ID: <16c2a469-802c-d21c-a200-fd2516af77dd@gmail.com> (raw)
In-Reply-To: <1a7063f7-1d7d-dbf4-a919-a55f733560f2@aklaver.com>
References: <0d08dd4d-3860-e85d-984d-0ed676dbdf1e@gmail.com>
<1a7063f7-1d7d-dbf4-a919-a55f733560f2@aklaver.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: track_activity_query_size max practical size?
In-Reply-To: <16c2a469-802c-d21c-a200-fd2516af77dd@gmail.com>
References: <0d08dd4d-3860-e85d-984d-0ed676dbdf1e@gmail.com> <1a7063f7-1d7d-dbf4-a919-a55f733560f2@aklaver.com> <16c2a469-802c-d21c-a200-fd2516af77dd@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox