Re: pg_dump output portability - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_dump output portability
Date
Msg-id 200208141816.g7EIGfL14938@candle.pha.pa.us
Whole thread Raw
In response to pg_dump output portability  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut wrote:
> I needed to move a PostgreSQL database to another product but I noticed
                                        ^^^^^^^^^^^^^^^^^^

Surely this is a misprint.  ;-)


> that the pg_dump output contains a few artifacts that make the output
> nonportable.  Most of these should be relatively easy to fix.  Here's my
> list:

Maybe we need a "maximum portability" flag for pg_dump that will do some
of the things outlined below.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: pg_dump output portability
Next
From: Bruce Momjian
Date:
Subject: Re: Open 7.3 items