On 04/26/2011 05:11 PM, Noah Misch wrote:
> On Mon, Apr 25, 2011 at 07:25:02PM -0400, Andrew Dunstan wrote:
>> I came across this today, while helping a customer. The following will
>> happily create a piece of XML with an embedded ^A:
>> select xmlelement(name foo, null, E'abc\x01def');
>> Now, a ^A is totally forbidden in XML version 1.0, and allowed but only
>> as "" or equivalent in XML version 1.1, and not as a 0x01 byte
>> ISTM this is something we should definitely try to fix ASAP, even if we
>> probably can't backpatch the fix.
> +1. Given that such a datum breaks dump+reload, it seems risky to do nothing at
> all in the back branches.
Here's a patch along the lines suggested by Peter.
I'm not sure what to do about the back branches and cases where data is
already in databases. This is fairly ugly. Suggestions welcome.
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2011-04-27 19:08:29|
|Subject: Re: pgsql: Fix pg_size_pretty() to avoid overflow for inputs close to INT64|
|Previous:||From: David Fetter||Date: 2011-04-27 19:04:54|
|Subject: Re: [HACKERS] PostgreSQL Core Team|