From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Date: Tue, 05 May 2020 17:31:26 -0400
Message-ID: <25857.1588714286@sss.pgh.pa.us> (raw)
In-Reply-To: <20200505194437.GA20275@alvherre.pgsql>
References: <20200505194437.GA20275@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2020-May-05, Bruce Momjian wrote:
>> I tried a few approaches but ended up with this:
>>
>> Improve control of prepared statement parameter logging (Alexey
>> Bashtanov, Álvaro Herrera)
>>
>> The GUC setting log_parameter_max_length controls the maximum
>> length of parameter values output during statement non-error
>> logging, and log_parameter_max_length_on_error does the same
>> for error statement logging. Previously, prepared statement
>> parameters were not logged during errors.
> This seems good to me. I think Tom Lane should be listed as coauthor of
> this item.
Not necessary, I didn't do much on that.
regards, tom lane
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: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, bruce@momjian.us, pryzby@telsasoft.com
Subject: Re: PG 13 release notes, first draft
In-Reply-To: <25857.1588714286@sss.pgh.pa.us>
* 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