Re: Re: log bind parameter values on error

From: David Steele <david(at)pgmasters(dot)net>
To: Alexey Bashtanov <bashtanov(at)imap(dot)cc>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: log bind parameter values on error
Date: 2019-03-29 10:38:55
Message-ID: 1c00de53-c5b5-55d8-91fb-887ec33d7590@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alexey,

On 3/14/19 12:38 PM, Peter Eisentraut wrote:
>
> Meanwhile, I have committed a patch that refactors the ParamListInfo
> initialization a bit, so you don't have to initialize hasTextValues in a
> bunch of places unrelated to your core code. So please rebase your
> patch on that.

It's been two weeks with no new patch or answers to Peter's questions.
Since we are nearly at the end of the CF I'll target this patch for PG13
and mark it Returned with Feedback at the end of the CF if there's no
new patch by then.

Regards,
--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2019-03-29 11:09:39 Re: Re: Row Level Security − leakproof-ness and performance implications
Previous Message Ashutosh Sharma 2019-03-29 10:27:56 table_privileges view always show object owner as a grantor