BUG #8654: pg_dumpall doesnt reliably replicate source database

From: craig(dot)miles0712(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #8654: pg_dumpall doesnt reliably replicate source database
Date: 2013-12-03 09:20:19
Message-ID: E1Vnm9T-00072D-0m@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 8654
Logged by: Craig Miles
Email address: craig(dot)miles0712(at)gmail(dot)com
PostgreSQL version: 9.2.4
Operating system: Ubuntu Precise
Description:

I used pg_dumpall (PG 9.3.1 version) to export from a 9.2.4 source database
cluster to a 9.3.1 target and found the following differences:

- Cluster username (under Maintenance database) is different.
- Template0 not exported resulting in differences in pg_database: encoding,
datcollate, datctype, datallowconn and datacl
- Template0 not even visible in the target server under PGAdmin for some
reason (I thought it was missing until I checked pg_database)
- All databases on target have default schema of "public" but don't on
source
- Maybe others ??

I would have thought that a high-level of confidence in the integrity of the
backup/restore process was paramount but I am left wondering what else may
be different?

Keep up the excellent work...

Craig

Browse pgsql-bugs by date

  From Date Subject
Next Message shaunc 2013-12-04 07:12:09 BUG #8655: pg_restore problems with materialized views
Previous Message Bruce Momjian 2013-12-03 02:43:42 Re: pg_upgrade error attempting to upgrade from PostgreSQL 9.1.6 with postgis 2.1.1 to PostgreSQL 9.3.0