Skip site navigation (1) Skip section navigation (2)

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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Date: 2007-11-01 23:28:09
Message-ID: 472A6109.2070601@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers

Bruce Momjian wrote:
>>>
>>> Is this a TODO?
>>>   
>>>       
>> No, we're long past this point. We've dropped 'convert ... using' entirely.
>>     
>
> The question is whether re-adding it should be a TODO.
>   

One of the reasons we dropped it was that the spec didn't seem to make 
sense. So if there's a proposal, first it would have to wait until we 
can get sane multi-locale support and then it would have to explain how 
it actually does what the spec says.

I don't think there's a definite TODO in that.

We don't seem to have had a single squawk since we dropped it, so I 
suspect it will be little mourned.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Hiroshi SaitoDate: 2007-11-02 01:23:39
Subject: Re: Calculation of a shared memory
Previous:From: Tom LaneDate: 2007-11-01 23:26:41
Subject: Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter

pgsql-committers by date

Next:From: User JbcooleyDate: 2007-11-02 00:41:16
Subject: npgsql - Npgsql2: 2007-11-1 Josh Cooley <jbnpgsql@tuxinthebox.net>
Previous:From: Tom LaneDate: 2007-11-01 23:26:41
Subject: Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group