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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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:26:41
Message-ID: 17313.1193959601@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Andrew Dunstan wrote:
>> No, we're long past this point. We've dropped 'convert ... using' entirely.

> The question is whether re-adding it should be a TODO.

Not unless someone wants it and can explain the spec convincingly.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2007-11-01 23:28:09 Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message Bruce Momjian 2007-11-01 23:23:14 Re: 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-11-01 23:28:09 Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message Bruce Momjian 2007-11-01 23:23:14 Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter