| 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:58:15 |
| Message-ID: | 922daef0-4093-d07c-4cf1-84c04fda8e5f@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
>
>>
>>> concerned about side effects of setting it to 48KB or even 64KB.
>>>
>>
>
--
Born in Arizona, moved to Babylonia.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-07-07 15:13:42 | Re: track_activity_query_size max practical size? |
| Previous Message | Ron | 2023-07-07 14:56:19 | Re: track_activity_query_size max practical size? |