| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Adrien NAYRAT <adrien(dot)nayrat(at)anayrat(dot)info> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-16 01:39:29 |
| Message-ID: | 20190116013929.GI1433@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 15, 2019 at 06:03:36PM +0100, Adrien NAYRAT wrote:
> The goal is not to find slow queries in a transaction, but troubleshoot
> applicative issue when you have short queries.
>
> Sometimes you want to understand what happens in a transaction, either you
> perfectly know your application, either you have to log all queries and find
> ones with the same transaction ID (%x). It could be problematic if you have
> a huge traffic with fast queries.
Looks like a sensible argument to me. High log throughput can cause
Postgres performance to go down by a couple of percents, which kills
the purpose of tracking down performance problems as this could impact
directly the application.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-01-16 01:48:24 | Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name |
| Previous Message | David Rowley | 2019-01-16 01:34:30 | Re: Proving IS NOT NULL inference for ScalarArrayOpExpr's |