From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Overriding default psql behavior | how to ignore missing fields |
Date: | 2010-12-31 21:17:58 |
Message-ID: | iflha6$723$1@reversiblemaps.ath.cx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2010-12-31, Håvard Wahl Kongsgård <haavard(dot)kongsgaard(at)gmail(dot)com> wrote:
> --90e6ba488359a7721f0498b43825
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
> I am trying to insert new records from multiple SQL dumps into an existing
> table. My problem is that the database table does not have some of the
> columns used in the sql dumps. So when I try to import the dumps psql fails
> with: "ERROR: current transaction is aborted, commands ignored until end o=
> f
> transaction block"
>
> As there are thousands of files with multiple missing fields, manually
> adding every field to the table is not a option.
In that case you'll need to do that automatically (write some software),
or find some other way to load the data.
> Is it possible to overriding the default psql behavior, so that the sql
> session simply ignores any missing fields?
no.
Perhaps load the tables into a temporary database and then copy the
columns you want, or drop the columns you dont and dump the whole
thing...
--
⚂⚃ 100% natural
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2010-12-31 21:30:40 | Re: Overriding default psql behavior | how to ignore missing fields |
Previous Message | Tom Lane | 2010-12-31 21:17:03 | Re: seg fault crashed the postmaster |