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

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 (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-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

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-11-01 23:28:09
Subject: Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous:From: Bruce MomjianDate: 2007-11-01 23:23:14
Subject: Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter

pgsql-committers by date

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