Re: Log a sample of transactions - Mailing list pgsql-hackers

From Adrien Mobile
Subject Re: Log a sample of transactions
Date
Msg-id B406A86A-3744-430F-AC18-DCD6120A6D1B@anayrat.info
Whole thread Raw
In response to Re: Log a sample of transactions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Log a sample of transactions  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Le 4 janvier 2019 13:20:09 GMT+01:00, Peter Eisentraut <peter.eisentraut@2ndquadrant.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
statementsof 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.


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Making all nbtree entries unique by having heap TIDs participatein comparisons
Next
From: "Daniel Verite"
Date:
Subject: Re: insensitive collations