pgsql: Adjust pg_dumpall so that it emits ENCODING, LC_COLLATE, and - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Adjust pg_dumpall so that it emits ENCODING, LC_COLLATE, and
Date
Msg-id 20090510025144.4F92F754067@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Adjust pg_dumpall so that it emits ENCODING, LC_COLLATE, and LC_CTYPE options
in its CREATE DATABASE commands only for databases that have settings
different from the installation defaults.  This is a low-tech method of
avoiding unnecessary platform dependencies in dump files.  Eventually we ought
to have a platform-independent way of specifying LC_COLLATE and LC_CTYPE, but
that's not going to happen for 8.4, and this patch at least avoids the issue
for people who aren't setting up per-database locales.  ENCODING doesn't have
the platform dependency problem, but it seems consistent to make it act the
same as the locale settings.

Modified Files:
--------------
    pgsql/src/bin/pg_dump:
        pg_dumpall.c (r1.124 -> r1.125)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_dumpall.c?r1=1.124&r2=1.125)

pgsql-committers by date:

Previous
From: h-saito@pgfoundry.org (User H-saito)
Date:
Subject: pg-migrator - pg_migrator: Ooops, miss coding...
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make a marginal performance improvement in predicate_implied_by