From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Use case for enabling log_duration other than benchmarking |
Date: | 2023-01-11 05:02:05 |
Message-ID: | CAOBaU_Y7MKeJVPB1sbLApJeR+Au_Mu93qYP7w3yubzh-r7cOQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le mer. 11 janv. 2023 à 00:28, Ron <ronljohnsonjr(at)gmail(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Vikas Sharma | 2023-01-11 08:43:09 | Re: Best opensource Postgresql monitoring tool |
Previous Message | Wiwwo Staff | 2023-01-10 18:01:24 | Disallow execution of shell commands from psql |