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: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Comparing two PostgreSQL databases -- order of pg_dump output
Date: 2011-08-30 23:07:21
Message-ID: 4E5D6D29.3080001@freedomcircle.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 08/30/2011 06:07 PM, Tom Lane wrote:
> Yeah, we've been around on that before.  pg_dump does actually sort the
> output items (modulo dependency requirements), but it sorts by the same
> "tag" values that are printed by pg_restore -l, and those aren't currently
> designed to be unique.  It's not too clear if we could get away with
> changing the definitions of the tag strings.

The approach suggested by Jaime works fairly well.  The only change I 
would make is to add OPERATOR args to the pg_restore -l output, e.g.,

1843; 2617 699799 OPERATOR public <(geometry, geometry) jma
1861; 2617 700565 OPERATOR public <(geography, geography) jma

Joe

In response to

pgsql-hackers by date

Next:From: Stephen FrostDate: 2011-08-30 23:11:07
Subject: Re: Comparing two PostgreSQL databases -- order of pg_dump output
Previous:From: Robert HaasDate: 2011-08-30 22:36:41
Subject: Re: spinlocks on HP-UX

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