| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Some 8.4 changes needed according to pg_migrator testing |
| Date: | 2009-05-08 17:34:24 |
| Message-ID: | 200905082034.26241.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 08 May 2009 19:09:51 Heikki Linnakangas wrote:
> How about only outputting the LC_COLLATE/CTYPE options for databases
> that use a non-default setting? In the common scenarios where you have
> the same collation for the whole cluster it would work just like in
> previous releases. If you dump and restore a database with default
> locale to a cluster initialized with a different locale, the database is
> restored with the default locale of the target cluster. But if you
> explicitly set a database to use a different locale, that would be
> preserved in dumps with the caveat that you'd have to change it manually
> if you restore to a cluster on a different platform.
That was my latest thinking as well. And it preserves the not-uncommon use
case that you pg_dumpall and restore your database after having initdb'ed with
a different locale/encoding in order to, say, switch to Unicode.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seth Robertson | 2009-05-08 17:47:28 | Re: [PATCH] Automatic client certificate selection support for libpq v1 |
| Previous Message | David Blewett | 2009-05-08 16:44:18 | Re: [PATCH] Automatic client certificate selection support for libpq v1 |