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 10:27:27 -0500
Message-ID: <a3922911-2f88-98fd-d988-b2fba377d2ed@gmail.com> (raw)
In-Reply-To: <2e3d60d4-24a3-884d-fec8-204de9635c67@aklaver.com>
References: <0d08dd4d-3860-e85d-984d-0ed676dbdf1e@gmail.com>
<1a7063f7-1d7d-dbf4-a919-a55f733560f2@aklaver.com>
<1cf118ea-91da-d9bf-2ed9-c079e2653964@aklaver.com>
<922daef0-4093-d07c-4cf1-84c04fda8e5f@gmail.com>
<2e3d60d4-24a3-884d-fec8-204de9635c67@aklaver.com>
On 7/7/23 10:13, Adrian Klaver wrote:
> On 7/7/23 07:58, Ron wrote:
>> On 7/7/23 09:55, Adrian Klaver wrote:
>>> 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?
>>
>> 10KB isn't enough to capture the whole query. Are there any bad side
>> effects of increasing it from 10KB to 48KB or 64KB?
>
> So to be clear the text of the query is large and not all of it is being
> being shown in pg_stat_activity.query. I have never had the need to
> increase that setting so all I can do is speculate. From the docs
> 'Specifies the amount of memory reserved to store the text of the
> currently executing command for each active session, ...'. So given a lot
> of active sessions with each query being a large text value there could be
> a side effect at some point. The bigger issue would seem to be 'This
> parameter can only be set at server start'. So you are looking at
> starting/stopping the server to find the sweet spot.
Restarting is something I can do during a quiet point after the bulk of the
day's work is complete, but before the nightly backups.
>
>>
>>>
>>>>
>>>>> 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: <a3922911-2f88-98fd-d988-b2fba377d2ed@gmail.com>
References: <0d08dd4d-3860-e85d-984d-0ed676dbdf1e@gmail.com> <1a7063f7-1d7d-dbf4-a919-a55f733560f2@aklaver.com> <1cf118ea-91da-d9bf-2ed9-c079e2653964@aklaver.com> <922daef0-4093-d07c-4cf1-84c04fda8e5f@gmail.com> <2e3d60d4-24a3-884d-fec8-204de9635c67@aklaver.com> <a3922911-2f88-98fd-d988-b2fba377d2ed@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