Re: log bind parameter values on error
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>, Alexey Bashtanov <bashtanov@imap.cc>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-09T17:31:12Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > On 2019-Dec-07, Tom Lane wrote: >> It is a very bad idea that this is truncating text without regard to >> multibyte character boundaries. > I see four possible ways forward, with nuances. In order of preference: > 1. change enough of the build system so that pg_encoding_mbcliplen is > available. (Offhand I see no reason why we couldn't move the > function from mbutils.c to wchar.c, but I haven't tried.) I'd be in favor of this if it doesn't turn out to require nasty contortions. My gut feeling (like yours, without having looked) is that the incremental amount of code to be moved into wchar.c wouldn't be much. BTW, not really the fault of this patch, but I wonder if we shouldn't make an effort to push the FRONTEND-available parts of wchar.c into src/common, just to make the system structure and build rules less confusing. I think the current situation only exists because this code predates our invention of src/common. regards, tom lane
Commits
-
Emit parameter values during query bind/execute errors
- ba79cb5dc841 13.0 landed
-
Add backend-only appendStringInfoStringQuoted
- 6cafde1bd43f 13.0 landed