Re: PG 13 release notes, first draft - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 13 release notes, first draft
Date
Msg-id 25857.1588714286@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG 13 release notes, first draft  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: PG 13 release notes, first draft  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Unify drop-by-OID functions
Next
From: Bruce Momjian
Date:
Subject: Re: PG 13 release notes, first draft