X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 58EB5329FB2 for ; Thu, 21 Oct 2004 23:18:41 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 85134-10 for ; Thu, 21 Oct 2004 22:18:33 +0000 (GMT) Received: from pop.sanbrunocable.com (pop.sanbrunocable.com [65.172.230.120]) by svr1.postgresql.org (Postfix) with ESMTP id B7192329FCE for ; Thu, 21 Oct 2004 23:18:33 +0100 (BST) Received: from oss4u.com (cpe-65-172-234-54.sanbrunocable.com [65.172.234.54]) by pop.sanbrunocable.com (8.11.6/8.11.6) with SMTP id i9LMH9G30748 for ; Thu, 21 Oct 2004 15:17:09 -0700 Received: (qmail 1898 invoked from network); 21 Oct 2004 22:14:55 -0000 Received: from tiburon.oss4u.com (192.168.1.4) by gw.oss4u.com (192.168.1.1) with ESMTP; 21 Oct 2004 22:14:55 -0000 From: "Uwe C. Schroeder" Organization: OSS4U, LLC To: Tom Lane Subject: Re: psql enhancement idea Date: Thu, 21 Oct 2004 15:18:32 -0700 User-Agent: KMail/1.5.3 Cc: pgsql-admin@postgresql.org References: <200410211205.09350.uwe@oss4u.com> <200410211500.20625.uwe@oss4u.com> <25850.1098396196@sss.pgh.pa.us> In-Reply-To: <25850.1098396196@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200410211518.32667.uwe@oss4u.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.6 tagged_above=0.0 required=5.0 tests=DOMAIN_4U2 X-Spam-Level: X-Archive-Number: 200410/291 X-Sequence-Number: 15284 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 21 October 2004 03:03 pm, Tom Lane wrote: > "Uwe C. Schroeder" writes: > > On Thursday 21 October 2004 12:40 pm, Tom Lane wrote: > >> 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 reason is that I made changes to the schema, i.e. changed the ordin= al > > position of columns and added some columns. Since the positioning of the > > columns isn't the same anymore a copy will fail. > > No, it won't, not if you use a column list. Ahhh - I see what you mean, thanks for that hint. A little remark then: the pg_dump manpage (7.4.3) states --attribute-inserts Dump data as INSERT commands with explicit column names (INS= ERT INTO table (column, ...) VALUES ...). This will make restorat= ion very slow, but it is necessary if you desire to rearrange = the column ordering. Maybe that should be fixed then. I was used to do the full insert statement= s=20 (ok, I've been using postgres long before it even had SQL) - maybe a old=20 habit then... Uwe - -- Open Source Solutions 4U, LLC 2570 Fleetwood Drive Phone: +1 650 872 2425 San Bruno, CA 94066 Cell: +1 650 302 2405 United States Fax: +1 650 872 2417 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFBeDW4jqGXBvRToM4RAu4+AJ9gchqGNrP/IUUYy8ySMWLyP6I0JgCdG1SH h0RLcQppb2yLaTkrG/W5cvc=3D =3D5tEF -----END PGP SIGNATURE-----