Re: track_activity_query_size max practical size?

2023-07-07 Thread Adrian Klaver
On 7/7/23 08:27, Ron wrote: 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. For completeness there is the auto_explain module: https://www.postgresql.org/docs/current/auto-explain.html -- Adrian Klaver

Re: track_activity_query_size max practical size?

2023-07-07 Thread Ron
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

Re: track_activity_query_size max practical size?

2023-07-07 Thread Adrian Klaver
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

Re: track_activity_query_size max practical size?

2023-07-07 Thread Ron
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

Re: track_activity_query_size max practical size?

2023-07-07 Thread Ron
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

Re: track_activity_query_size max practical size?

2023-07-07 Thread Adrian Klaver
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,

Re: track_activity_query_size max practical size?

2023-07-07 Thread Adrian Klaver
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

track_activity_query_size max practical size?

2023-07-07 Thread Ron
We've got some Very Large Queries that take a long time.  Even setting taqs to 10KB isn't adequate, so I want to significantly bump it, but am concerned about side effects of setting it to 48KB or even 64KB. -- Born in Arizona, moved to Babylonia.