Message-ID: <4A65F9CB.2050000@gmail.com>
Date: Tue, 21 Jul 2009 11:24:27 -0600
From: Rob Sargent <robjsargent@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-sql@postgresql.org
References: <4A65EC7A.8010003@gmail.com> <15027.1248194992@sss.pgh.pa.us>
In-Reply-To: <15027.1248194992@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Order of operations in ascii vs archive format (moderately
 urgent)

The ascii dump has serveral CREATE FUNCTION gbtreeN_{in,out} but I don't 
see them in the current (source) database using '\df gbtree*'.  Using 
'\df gbt*' I get 111 functions for which all the names begin 'gbt_'.  
Have I lost them? The gbtreekeyN types are still there. 

Tom Lane wrote:
> Rob Sargent <robjsargent@gmail.com> writes:
>   
>> Is there a difference in the order of execution between an ascii dump 
>> and one using the "custom" format?  Or any difference in the general 
>> operation? 
>>     
>
> There's not supposed to be.  One standard test on the pg_dump code is
> 	pg_dump >textfile
> 	pg_dump -Fc >dumpfile
> 	pg_restore dumpfile >textfile2
> 	diff textfile textfile2
> If these don't produce the same results something is broken.
>
> 			regards, tom lane
>