Re: type money causes unrestorable dump

From: Gregory Stark <stark(at)enterprisedb(dot)com>
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>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: type money causes unrestorable dump
Date: 2007-11-03 19:26:31
Message-ID: 87abpvruzc.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> A more direct approach to the problem might be to change pg_dump to
> set lc_monetary, as it does for client_encoding ...

It should probably note that if the machine being restored onto has a
different libc it could still not be restorable even with the correct
lc_monetary setting.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-03 19:27:10 CREATE CONSTRAINT TRIGGER compatibility issue
Previous Message Tom Lane 2007-11-03 18:39:48 Re: type money causes unrestorable dump