Re: PG 13 release notes, first draft

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 13 release notes, first draft
Date: 2020-05-05 21:31:26
Message-ID: 25857.1588714286@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-05-05 21:34:26 Re: PG 13 release notes, first draft
Previous Message Alvaro Herrera 2020-05-05 21:10:57 Re: Unify drop-by-OID functions