| From: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Edge case problem with pg_dump |
| Date: | 2002-05-23 11:32:45 |
| Message-ID: | 20020523113246.57AB01C73@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at){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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Burton | 2002-05-23 13:07:11 | Re: no pg_hba.conf |
| Previous Message | Daniel Kalchev | 2002-05-23 10:19:15 | tuples gone? |