Re: [PATCH]: Allow errors in parameter values to be reported during the BIND phase itself..
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Alexey Bashtanov <bashtanov@imap.cc>,
Franck Verrot <franck@verrot.fr>,
pgsql-hackers@postgresql.org
Date: 2021-03-16T00:30:18Z
Lists: pgsql-hackers
Attachments
- 0001-identify-bad-bind-parameters.patch (text/x-diff) patch 0001
Justin Pryzby <pryzby@telsasoft.com> writes: > On Mon, Mar 15, 2021 at 06:45:49PM -0400, Tom Lane wrote: >> I started to look at this, and immediately began to wonder where is the >> previous discussion you're evidently referring to. Can you dig up an >> archives link? > I think I was referring to this (from the commit message). > https://www.postgresql.org/message-id/flat/CANfkH5k-6nNt-4cSv1vPB80nq2BZCzhFVR5O4VznYbsX0wZmow@mail.gmail.com Got it, thanks. After studying the patch it seems like there's a better way to do it: we should just log the single parameter that's at fault. That saves the user from having to dig through a bunch of parameters to figure out which one we're complaining about, plus we can usefully identify the parameter (by number) even if it was sent in binary. This is a little bit more net code addition than what you had, but only by ten lines or so. On the plus side, it doesn't require rearranging any existing code. regards, tom lane
Commits
-
Improve logging of bad parameter values in BIND messages.
- 1ea396362be1 14.0 landed