| 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 23:08:55 |
| Message-ID: | 46F05A87.1050306@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> OTOH we may be talking at cross-purposes --- on looking into gram.y
> I see that this syntax is transformed to a call of convert_using(),
> which may mean it has nothing to do with your changes.
>
>
>
No, I changed convert_using -
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/pg_conversion.c?r1=1.36&r2=1.37
We can revert that if necessary. It will open up a hole, though. Take
your pick - spec compliance or validly coded data.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-18 23:25:36 | Re: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter |
| Previous Message | Tom Lane | 2007-09-18 23:02:53 | Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-18 23:13:51 | Re: pg_ctl -w vs unix_socket_directory |
| Previous Message | Tom Lane | 2007-09-18 23:02:53 | Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter |