Noah Misch <n...@leadboat.com> writes: > On Fri, Feb 21, 2014 at 05:20:06PM -0500, Tom Lane wrote: >> ... However, I think there's a case to be >> made for adding the additional pg_verify_mbstr() calls in the back >> branches. We've been promising since around 8.3 that invalidly encoded >> data can't get into a database, and it's disturbing to find that there >> are leaks in that.
> I had a dark corner of an app break from the 8.4-vintage change to make > E'abc\000def'::text raise an error rather than truncate the string. The old > behavior was clearly wrong, but I was still glad the change arrived in a major > release; the truncation happened to be harmless for that app. Adding > pg_verify_mbstr() calls creates a similar situation. Since I'm not hearing anybody else argue for a back-patch, I've committed this in HEAD only. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers