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

Re: Mention pg_dump version portability

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Mention pg_dump version portability
Date: 2006-05-16 18:46:33
Message-ID: 20060516184633.GM26212@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
On Mon, May 15, 2006 at 07:43:20PM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > On Sat, May 13, 2006 at 12:21:06PM -0400, Bruce Momjian wrote:
> > > I have applied this patch that mentions pg_dump portability to 8.1.X and
> > > CVS HEAD.
> > 
> > Would it be worth recommending using the custom format over plain? I see
> > plenty of issues with incompatabilities in the plain version, but I
> > don't think I've ever seen problem with the custom format (though this
> > could just be because everyone uses the default...)
> 
> Right, it is just because it is the default.

But shouldn't the custom format deal better with version changes, or
does the format of custom change just as often? Though, even if it did
change just as often, pg_restore should be able to deal better with it
than psql, since pg_restore knows it's a dump and knows what version
it's coming from...
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

In response to

Responses

pgsql-docs by date

Next:From: Tom LaneDate: 2006-05-16 23:18:48
Subject: Re: Mention pg_dump version portability
Previous:From: Bruce MomjianDate: 2006-05-15 23:43:20
Subject: Re: Mention pg_dump version portability

pgsql-hackers by date

Next:From: Gurjeet SinghDate: 2006-05-16 18:49:52
Subject: Re: [BUGS] BUG #2429: Explain does not report object's schema
Previous:From: Jeff FrostDate: 2006-05-16 18:22:27
Subject: Re: does wal archiving block the current client connection?

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