| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: invalidly encoded strings |
| Date: | 2007-09-10 03:38:08 |
| Message-ID: | 1189395488.5924.27.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Sun, 2007-09-09 at 23:22 -0400, Tom Lane wrote:
> In the short run it might be best to do it in scan.l after all. A few
> minutes' thought about what it'd take to delay the decisions till later
> yields a depressingly large number of changes; and we do not have time
> to be developing mostly-cosmetic patches for 8.3. Given that
> database_encoding is frozen for any one DB at the moment, and that that
> is unlikely to change in the near future, insisting on a solution that
> allows it to vary is probably unreasonable at this stage of the game.
>
Sounds reasonable to me.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-10 03:43:48 | Re: invalidly encoded strings |
| Previous Message | Andrew Dunstan | 2007-09-10 03:33:20 | Re: invalidly encoded strings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-10 03:43:48 | Re: invalidly encoded strings |
| Previous Message | Andrew Dunstan | 2007-09-10 03:33:20 | Re: invalidly encoded strings |