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

Andrew Dunstan wrote:
> 
> 
> 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.

Is this a TODO?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +