| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: type money causes unrestorable dump |
| Date: | 2007-11-03 21:37:32 |
| Message-ID: | 200711032237.33281.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Doing it would be a problem
> when transporting dump files across platforms: what if the
> appropriate locale name is spelled differently on the new machine?
The question is which is more likely?
Using a dump on a similar platform with different locale settings is
fairly common, especially by accident. (And this is a problem that is
easily masked if you don't run the restore with on-error-stop.)
Using a dump on a platform with different locale spellings is, in my
mind, rarer. And even then, if you have different locale spellings,
chances are, you have semantically different locales configured.
What could help is if we could invoke this only if the money type is
actually used.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ohp | 2007-11-03 21:47:46 | Re: should I worry? |
| Previous Message | Tom Lane | 2007-11-03 19:47:40 | Re: type money causes unrestorable dump |