Re: Order of operations in ascii vs archive format (moderately urgent)

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Order of operations in ascii vs archive format (moderately urgent)
Date: 2009-07-21 17:24:27
Message-ID: 4A65F9CB.2050000@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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(at)gmail(dot)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
>

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2009-07-21 17:29:43 Re: Order of operations in ascii vs archive format (moderately urgent)
Previous Message Rob Sargent 2009-07-21 16:54:47 Re: Order of operations in ascii vs archive format (moderately urgent)