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 46F05201.6050305@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: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
List pgsql-hackers

Tom Lane wrote:
> adunstan@postgresql.org (Andrew Dunstan) writes:
>   
>> Log Message:
>> The two argument form of convert() is gone,
>>     
>
> Um ... so that means CONVERT(c USING y) now fails entirely?  That might
> be going a bit far.  If we do want to get rid of that syntax then I'm
> noting a lack of parser changes in this patch.
>
>             
>   

No, that's still there. The only change there is that it returns a 
bytea. I forgot to put that in the commit notes. :-( And the fact that 
it's still there is confirmed by the fact that we don't have regression 
failures ;-)

cheers

andrew


pgsql-hackers by date:

Previous
From: Radoslaw Zielinski
Date:
Subject: pg_ctl -w vs unix_socket_directory
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_ctl -w vs unix_socket_directory