From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: query logging of prepared statements |
Date: | 2019-04-07 16:09:57 |
Message-ID: | 20190407160957.GA32275@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 2019-Apr-07, Justin Pryzby wrote:
> [...] Since I've been using log_statement=all, and not
> log_min_duration_statement, I don't have a strong opinion about it.
Ah, so your plan for this in production is to use the sample-based
logging facilities, I see! Did you get Adrien a beer already?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Izmailov | 2019-04-07 18:45:53 | assembling PGresults from multiple simultaneous queries (libpq, singlerowmode) |
Previous Message | Justin Pryzby | 2019-04-07 15:31:01 | Re: query logging of prepared statements |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2019-04-07 16:11:29 | Re: ToDo: show size of partitioned table |
Previous Message | Tom Lane | 2019-04-07 16:09:40 | Re: Speed up transaction completion faster after many relations are accessed in a transaction |