Re: PG 16 draft release notes ready - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: PG 16 draft release notes ready
Date
Msg-id ZHXJ522uSKnLgIzt@momjian.us
Whole thread Raw
In response to Re: PG 16 draft release notes ready  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 16 draft release notes ready
List pgsql-hackers
On Sat, May 27, 2023 at 09:34:37PM -0400, Bruce Momjian wrote:
> > > This is controlled by auto_explain.log_parameter_max_length, and by
> > > default query parameters will be logged with no length
> > > restriction. SHOULD THIS BE MORE CLEARLY IDENTIFIED AS CONTROLLING THE
> > > EXECUTION OF PREPARED STATEMENTS?
> > 
> > This is wrong, the logging applies to all query parameters, not just for
> > prepared statements (and has nothing to do with controlling the
> > execution thereof).  That was just the only way to test it when it was
> > written, because psql's \bind command exist yet then.
> 
> I see your point.  How is this?
> 
>     Allow auto_explain to log query parameters used by parameterized
>     statements (Dagfinn Ilmari Mannsåker)
> 
>     This affects queries using server-side PRAPARE/EXECUTE
>     and client-side parse/bind.  Logging is controlled by
>     auto_explain.log_parameter_max_length;    by default query
>     parameters will be logged with no length restriction.

Done, attached patch applied.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.

Attachment

pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: ERROR: no relation entry for relid 6
Next
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: PG 16 draft release notes ready