From: Tom Lane <tgl@sss.pgh.pa.us>
To: Uwe C. Schroeder <uwe@oss4u.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: psql enhancement idea
Date: Thu, 21 Oct 2004 15:40:14 -0400
Message-ID: <22591.1098387614@sss.pgh.pa.us> (raw)
In-Reply-To: <200410211205.09350.uwe@oss4u.com>
References: <200410211205.09350.uwe@oss4u.com>
"Uwe C. Schroeder" <uwe@oss4u.com> writes:
> I'm just doing a load of database transfers using pg_dump. Because I changed
> the schema of quite some tables I have to dump full column inserts.
I don't think that conclusion follows from that premise. In recent
pg_dump versions (any that use a column list with COPY, which I think is
7.3 or later) there is no fundamental disadvantage to using COPY; it
should be semantically equivalent to INSERT-with-column-list commands.
The only reason I can see for using the INSERT option anymore is if you
think that some of the row insertions might fail, and you don't want
that to stop the load altogether. If that's what you want, then you'd
certainly not want to wrap the load in BEGIN/END, so there doesn't seem
to be much point in adding an option to do it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, uwe@oss4u.com
Subject: Re: psql enhancement idea
In-Reply-To: <22591.1098387614@sss.pgh.pa.us>
References: <200410211205.09350.uwe@oss4u.com> <22591.1098387614@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox