| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
| Subject: | Re: Log a sample of transactions |
| Date: | 2019-01-04 12:20:09 |
| Message-ID: | 6eb78524-6871-4914-6ce7-f88ed54d811e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/12/2018 22:32, Adrien Nayrat wrote:
> Per idea of Nikolay Samokhvalov[1] I propose this patch to add the possibility
> to log all statements from a fraction of transactions.
>
> I have several questions:
> * Do we want this feature?
It's not clear to me what the use is. The per-statement sampling allows
you to capture slow queries without overwhelming the logs. We don't
have any logging of slow transactions or any other transaction scope
logging, so what will this sample?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kristjan Tammekivi | 2019-01-04 12:20:55 | Re: Potentially undocumented behaviour change in Postgres 11 concerning OLD record in an after insert trigger |
| Previous Message | Alvaro Herrera | 2019-01-04 12:19:25 | Re: don't create storage when unnecessary |