From: Andres Freund <andres@anarazel.de>
To: Alexey Bashtanov <bashtanov@imap.cc>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: log bind parameter values on error
Date: Thu, 14 Feb 2019 12:23:52 -0800
Message-ID: <20190214202352.xo7dxcvztziyqdxr@alap3.anarazel.de> (raw)
In-Reply-To: <0146a67b-a22a-0519-9082-bc29756b93a2@imap.cc>
References: <0146a67b-a22a-0519-9082-bc29756b93a2@imap.cc>
Hi,
On 2018-12-14 23:04:26 +0000, Alexey Bashtanov wrote:
> Unfortunately, when enabled, the feature comes with some memory and CPU
> overhead,
> as we cannot convert certain values to text when in aborted transaction.
Have you analyzed how invasive it'd be to delay that till we actually
can safely start a [sub]transaction to do that logging? Probably too
expensive, but it seems like something that ought to be analyzed.
- Andres
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andres@anarazel.de, bashtanov@imap.cc
Subject: Re: log bind parameter values on error
In-Reply-To: <20190214202352.xo7dxcvztziyqdxr@alap3.anarazel.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox