Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Date
Msg-id 46F05A87.1050306@dunslane.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
List pgsql-hackers

Tom Lane wrote:
> OTOH we may be talking at cross-purposes --- on looking into gram.y
> I see that this syntax is transformed to a call of convert_using(),
> which may mean it has nothing to do with your changes.
>
>     
>   

No, I changed convert_using - 
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_conversion.c?r1=1.36&r2=1.37

We can revert that if necessary. It will open up a hole, though. Take 
your pick - spec compliance or validly coded data.

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Next
From: Radoslaw Zielinski
Date:
Subject: Re: pg_ctl -w vs unix_socket_directory