Re: Use case for enabling log_duration other than benchmarking - Mailing list pgsql-general

From Julien Rouhaud
Subject Re: Use case for enabling log_duration other than benchmarking
Date
Msg-id CAOBaU_Y7MKeJVPB1sbLApJeR+Au_Mu93qYP7w3yubzh-r7cOQg@mail.gmail.com
Whole thread Raw
In response to Re: Use case for enabling log_duration other than benchmarking  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
Le mer. 11 janv. 2023 à 00:28, Ron <ronljohnsonjr@gmail.com> a écrit :
If your application requires subsecond response, and you're only getting subsecond response some of the time, then you obviously want to know why.  Part of that is checking to see if the database and queries are doing their job.

now that log_line_prefix can display the query_id, it could also be used to get a limited version of what log_min_duration_statements does (you can know what query was but not the exact parameters), but in a way cheaper way. of course it assumes that you have something like pg_stat_statements installed and that you need some more granularity than regular snapshots of its information. 

pgsql-general by date:

Previous
From: Wiwwo Staff
Date:
Subject: Disallow execution of shell commands from psql
Next
From: Vikas Sharma
Date:
Subject: Re: Best opensource Postgresql monitoring tool