Re: Edge case problem with pg_dump - Mailing list pgsql-hackers

From D'Arcy J.M. Cain
Subject Re: Edge case problem with pg_dump
Date
Msg-id 20020523113246.57AB01C73@druid.net
Whole thread Raw
In response to Re: Edge case problem with pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Edge case problem with pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On May 22, 2002 10:28 am, you wrote:
> Right now the only safe way to dump such a database is to use the
> inserts-with-explicit-column-names option.  Someone was working on
> extending COPY to allow a column name list, and as soon as that gets
> done I intend to change pg_dump to specify a column name list in
> COPY commands.  That should fix this problem.

Do you mean issue COPY commands with fields or COPY out the fields in a 
specific order by using the extension in pg_dump?  Seems like the latter 
would be cleaner but the former is probably a lot simpler to do.

What would the new syntax of the COPY look like?

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.


pgsql-hackers by date:

Previous
From: Daniel Kalchev
Date:
Subject: tuples gone?
Next
From: Ulrich Drepper
Date:
Subject: Re: Redhat 7.3 time manipulation bug