"D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> wrote:
>> A more direct approach to the problem might be to change pg_dump to
>> set lc_monetary, as it does for client_encoding ...
> Certainly OK by me.
Greg's objection caused me to rethink that. 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? We should
probably leave it in the user's hands to get this right. So the added
text could be used as I suggested, or tweaked to say that you must set
lc_monetary to something equivalent to the prior setting.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
