Re: (A) native Windows port - Mailing list pgsql-hackers

From Oliver Elphick
Subject Re: (A) native Windows port
Date
Msg-id 1025903925.31483.68.camel@linda
Whole thread Raw
In response to Re: (A) native Windows port  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
On Fri, 2002-07-05 at 17:39, Lamar Owen wrote:
> No, what I envisioned was a standalone dumper that can produce dump output 
> without having a backend at all.  If this dumper knows about the various 
> binary formats, and knows how to get my data into a form I can then restore 
> reliably, I will be satisfied.  If it can be easily automated so much the 
> better.  Doing it table by table would be ok as well.
...
> 1.)    Must not require the old version executable backend.  There are a number 
> of reasons why this might be, but the biggest is due to the way much 
> upgrading works in practice -- the old executables are typically gone by the 
> time the new package is installed.
> 
> 2.)    Uses pg_dbdump of the new version.  This dumper can be tailored to provide 
> the input pg_restore wants to see.  The dump-restore sequence has always had 
> dumped-data version mismatch as its biggest problem -- there have been issues 
> before where you would have to install the new version of pg_dump to run 
> against the old backend.  This is unacceptable in the real world of binary 
> packages.

I concur completely!

As a package maintainer, this would remove my biggest problem.


Oliver Elphick
(Debian maintainer)






pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: (A) native Windows port
Next
From: Andrew Sullivan
Date:
Subject: Re: (A) native Windows port