From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Mention pg_dump version portability
Date: Tue, 16 May 2006 19:18:48 -0400
Message-ID: <13191.1147821528@sss.pgh.pa.us> (raw)
In-Reply-To: <20060516184633.GM26212@pervasive.com>
References: <20060515202354.GM26212@pervasive.com>
<200605152343.k4FNhK703441@candle.pha.pa.us>
<20060516184633.GM26212@pervasive.com>
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> But shouldn't the custom format deal better with version changes, or
> does the format of custom change just as often?
It's completely orthogonal, because the SQL involved is just the same.
One of the tests I periodically run is to compare
pg_dump >foo
pg_dump -Fc | pg_restore >bar
and make sure the outputs are word-for-word the same.
What custom or tar format buys you is the flexibility of extracting
different subsets of the dump after-the-fact, using pg_restore's
switches. Of course you can do that with a text editor on a plain
dump, if the dump's not too large for your editor to handle ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, jnasby@pervasive.com, pgman@candle.pha.pa.us
Subject: Re: Mention pg_dump version portability
In-Reply-To: <13191.1147821528@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox