Re: BUG #5198: Plain dump: wrong field order for inherited tables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Lyamin Mikhail" <lma032(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5198: Plain dump: wrong field order for inherited tables
Date: 2009-11-19 15:13:39
Message-ID: 14573.1258643619@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Lyamin Mikhail" <lma032(at)gmail(dot)com> writes:
> 1) create table
> 2) create inherited table
> 3) add fields in parent table
> 4) add fields in child table
> 5) make dump

> Now you have wrong order of fields in insert.

AFAIK this will happen only if you use the --inserts switch, which is
deprecated for exactly this reason. Let it use COPY as it will do
by default, or use --column-inserts if you must have insert statements.

If you think there's a problem without --inserts, you need to show an
exact example, not hand-waving.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Iliya Krapchatov 2009-11-19 17:11:51 BUG #5199: Window frame clause wrong (?) behaviour
Previous Message Valaki Valahol 2009-11-19 14:16:08 Stored procedure error