Received: from peer1.mail.home.com (ldap1-sfba.mail.home.com [24.0.95.130]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA9AC3s21701 for ; Thu, 9 Nov 2000 05:12:03 -0500 (EST) (envelope-from fspam@home.com) Received: from tajar ([24.1.6.224]) by femail2.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001109035442.MCDY14736.femail2.sdc1.sfba.home.com@tajar> for ; Wed, 8 Nov 2000 19:54:42 -0800 From: Forest Wilkinson To: pgsql-sql@postgresql.org Subject: alter table add column implementation undesirable? Date: Wed, 08 Nov 2000 19:55:22 -0800 Message-ID: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200011/68 X-Sequence-Number: 99 A coworker told me that the postgres implementation of ALTER TABLE ADD COLUMN creates an inefficient database. He said it results in a table whose new column is stored someplace other than the rest of the columns. (A hidden auxiliary table?) Is this true in postgres 6.5.3? 7.x? Was it ever true? Forest Wilkinson