Skip site navigation (1) Skip section navigation (2)

Re: Comparing two PostgreSQL databases -- order of pg_dump output

From: Joe Abbate <jma(at)freedomcircle(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Comparing two PostgreSQL databases -- order of pg_dump output
Date: 2011-08-31 14:42:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 08/31/2011 10:17 AM, Tom Lane wrote:
> Short of that sort of anal-retentiveness, there are going to be cases
> where the dump order is a bit unpredictable.  IMO what we need is a
> reasonable compromise between verbosity and uniqueness, such that in
> normal cases (ie, where you *didn't* intentionally create near-identical
> functions in different schemas) you get a unique ordering.  To get to
> that, somebody's got to go through all the tag writing code and identify
> where the trouble spots are.  So far we've heard triggers and operators
> nominated ... what else?

So far, for Pyrseas, I've tested aggregates, casts, constraint triggers, 
conversions, domains, functions, indexes, languages, operators, rules, 
schemas, sequences, tables (including check constraints, primary keys, 
foreign keys, unique constraints and inherited tables), triggers, types 
(base and composite), views and comments on the various objects.  I'll 
be testing operator classes and operator families in the coming weeks. 
So far, triggers and operators are the only ones that have caused an 
issue when using the technique suggested by Jaime (pg_dump -Fc followed 
by pg_restore -l).  Functions also caused problems in the plain text 
pg_dump, e.g., because funcx(geography) sorts after funcx(geometry) if 
the latter is created first.


In response to


pgsql-hackers by date

Next:From: Jeff DavisDate: 2011-08-31 15:09:15
Subject: Re: casting between range types
Previous:From: Tom LaneDate: 2011-08-31 14:17:36
Subject: Re: Comparing two PostgreSQL databases -- order of pg_dump output

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group