From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: Bruce Momjian <bruce@momjian.us>, Justin Pryzby <pryzby@telsasoft.com>,
        PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
In-reply-to: <20200505194437.GA20275@alvherre.pgsql>
References: <20200505194437.GA20275@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
	message dated "Tue, 05 May 2020 15:44:37 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25856.1588714286.1@sss.pgh.pa.us>
Date: Tue, 05 May 2020 17:31:26 -0400
Message-ID: <25857.1588714286@sss.pgh.pa.us>
Precedence: bulk

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, &Aacute;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