| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, laurenz(dot)albe(at)wien(dot)gv(dot)at, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-18 18:04:32 |
| Message-ID: | 46F01330.1090207@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Anyway, on the strength of that, these functions are definitely
> best named to stay away from the spec syntax, so +1 for your
> proposal above.
>
>
>
OK, I have committed this and the other the functional changes that
should change the encoding holes.
Catalog version bumped.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2007-09-18 18:17:20 | Re: 8.3 version of ts_headline |
| Previous Message | Andrew Dunstan | 2007-09-18 17:41:17 | pgsql: Close previously open holes for invalidly encoded data to enter |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-09-19 01:27:33 | Incorrect results from corr() |
| Previous Message | Tom Lane | 2007-09-18 15:22:45 | Re: invalidly encoded strings |