Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA9FW5s54446 for ; Thu, 9 Nov 2000 10:32:05 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eA9FVN506330; Thu, 9 Nov 2000 10:31:23 -0500 (EST) To: Forest Wilkinson cc: pgsql-sql@postgresql.org Subject: Re: alter table add column implementation undesirable? In-reply-to: References: Comments: In-reply-to Forest Wilkinson message dated "Wed, 08 Nov 2000 19:55:22 -0800" Date: Thu, 09 Nov 2000 10:31:23 -0500 Message-ID: <6327.973783883@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/71 X-Sequence-Number: 102 Forest Wilkinson writes: > A coworker told me that the postgres implementation of ALTER TABLE ADD > COLUMN creates an inefficient database. Dunno where he got that idea. There are some problems lurking in ADD COLUMN when used on a table with inheritance children --- the new column is added to the children too, as it should be, but in an unexpected column position, which causes trouble for pg_dump (a dump and reload will do the wrong thing). Perhaps what you heard is a garbled report of that issue. regards, tom lane