From: | Adrien Mobile <adrien(dot)nayrat(at)anayrat(dot)info> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "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 15:57:03 |
Message-ID: | B406A86A-3744-430F-AC18-DCD6120A6D1B@anayrat.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Le 4 janvier 2019 13:20:09 GMT+01:00, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> a écrit :
>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
Hello,
When you troubleshoot applicative issues with multi-statements transaction, you may have to log all queries to find all statements of one transaction. With high throughput, it could be hard to log all queries without causing troubles.
The goal of this patch is to be able to log a sample of transactions. I agree the use case is specific.
Regards
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2019-01-04 16:05:08 | Re: insensitive collations |
Previous Message | Alexander Korotkov | 2019-01-04 15:40:16 | Re: Making all nbtree entries unique by having heap TIDs participate in comparisons |