From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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:35:02 |
Message-ID: | 20200505213502.GM21185@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 5, 2020 at 05:31:26PM -0400, Tom Lane wrote:
> 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, Á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.
OK, removed.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2020-05-05 21:39:58 | Re: PG 13 release notes, first draft |
Previous Message | Bruce Momjian | 2020-05-05 21:34:26 | Re: PG 13 release notes, first draft |