| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ingo van Lil <inguin(at)gmx(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Inherited tables and pg_dump |
| Date: | 2002-05-23 02:33:21 |
| Message-ID: | 1884.1022121201@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Ingo van Lil <inguin(at)gmx(dot)de> writes:
> We've got a table that inherits another one, and we had to add a new
> column to the mother table (and thus to the son, too). Now, if we dump
> the database, the columns of the INSERT resp. COPY commands for the data
> of the son table are in wrong order.
Right at the moment you have to use pg_dump's -D option to deal with
this situation. See discussion earlier today...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edwin Groothuis | 2002-05-23 04:43:15 | Re: Bug #670: netmask displayed for a /32 |
| Previous Message | Ingo van Lil | 2002-05-22 23:48:54 | Inherited tables and pg_dump |