| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump output portability |
| Date: | 2002-08-14 18:16:41 |
| Message-ID: | 200208141816.g7EIGfL14938@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-14 18:24:50 | Re: Open 7.3 items |
| Previous Message | Joe Conway | 2002-08-14 18:09:41 | Re: [HACKERS] [GENERAL] workaround for lack of REPLACE() function |