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: Andrew Dunstan <andrew(at)dunslane(dot)net>
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:18:34
Message-ID: 11125.1190153914@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-18 22:32:33 Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Previous Message User Cunha17 2007-09-18 18:33:25 snapshot - src: Fix for [#1008312] Disable internal NOTICE messages in

Browse pgsql-hackers by date

  From Date Subject
Next Message Radoslaw Zielinski 2007-09-18 22:24:54 pg_ctl -w vs unix_socket_directory
Previous Message Decibel! 2007-09-18 22:08:11 Re: Open issues for HOT patch