| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, Vitali Stupin <vitali(dot)stupin(at)ria(dot)ee>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns |
| Date: | 2006-10-16 14:28:06 |
| Message-ID: | 20263.1161008886@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> It's clear whether you actually want to allow people to put utf8
> characters directly into their source (especially if the database is
> not in utf8 encoding anyway). There is always the \u{xxxx} escape.
Well, if the database encoding isn't utf8 then we'd not issue any such
command anyway. But if it is, then AFAICS the text of pg_proc entries
could be expected to be utf8 too.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ergin Ozekes | 2006-10-16 14:52:08 | BUG #2696: odbc driver cannot connect |
| Previous Message | Tom Lane | 2006-10-16 14:24:02 | Re: BUG #2694: Memory allocation error when selecting array of empty arrays |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Harvell F | 2006-10-16 14:55:05 | Re: Postgresql Caching |
| Previous Message | Martijn van Oosterhout | 2006-10-16 14:10:44 | Re: [HACKERS] BUG #2683: spi_exec_query in plperl returns |