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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Date: 2007-09-18 22:32:33
Message-ID: 46F05201.6050305@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> adunstan(at)postgresql(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-09-18 23:02:53 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message Tom Lane 2007-09-18 22:18:34 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-18 22:42:14 Re: pg_ctl -w vs unix_socket_directory
Previous Message Radoslaw Zielinski 2007-09-18 22:24:54 pg_ctl -w vs unix_socket_directory