| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Jim Mlodgenski <jimmy76(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Client Messages |
| Date: | 2012-01-26 17:49:45 |
| Message-ID: | 1327600185.26839.2.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tor, 2012-01-26 at 10:34 +0200, Heikki Linnakangas wrote:
> For postgresql.conf I think we could make a rule that it's always in
> UTF-8. We haven't had to take a stance on the encoding used in
> postgresql.conf before, but IMHO UTF-8 only would be quite reasonable.
We have so far violently resisted forcing UTF-8 anywhere, and this
doesn't seem like a good place to start.
We could perhaps recognize an encoding declaration like this in the
file:
http://docs.python.org/reference/lexical_analysis.html#encoding-declarations
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-01-26 17:49:46 | Re: pg_bulkload ON_DUPLICATE_MERGE |
| Previous Message | Robert Haas | 2012-01-26 17:47:55 | Re: Different error messages executing CREATE TABLE or ALTER TABLE to create a column "xmin" |