Re: Log a sample of transactions

From: Adrien NAYRAT <adrien(dot)nayrat(at)anayrat(dot)info>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, "Nikolay Samokhvalov" <samokhvalov(at)gmail(dot)com>
Subject: Re: Log a sample of transactions
Date: 2019-01-18 13:22:50
Message-ID: 9640082a-c4c2-4037-e464-f00ab48e8569@anayrat.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/18/19 9:03 AM, Peter Eisentraut wrote:
> But if you have trouble with a specific transaction, how will a setting
> help that randomly logs transactions, not necessarily the one you are
> concerned about?

Yes, it assumes your application performs same type of transaction.
Maybe the use case is too specific to have this feature in core?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rahila Syed 2019-01-18 14:07:19 Re: monitoring CREATE INDEX [CONCURRENTLY]
Previous Message Etsuro Fujita 2019-01-18 12:55:28 Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0