Received: from acheron.rime.com.au (albatr.lnk.telstra.net [139.130.54.222]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f077tG770704 for ; Sun, 7 Jan 2001 02:55:17 -0500 (EST) (envelope-from pjw@rhyme.com.au) Received: from oberon (Oberon.rime.com.au [203.8.195.100]) by acheron.rime.com.au (8.9.3/8.9.3) with SMTP id SAA19035; Sun, 7 Jan 2001 18:55:36 +1100 Message-Id: <3.0.5.32.20010107185544.03968700@mail.rhyme.com.au> X-Sender: pjw@mail.rhyme.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sun, 07 Jan 2001 18:55:44 +1100 To: Tatsuo Ishii , pgsql-hackers@postgresql.org From: Philip Warner Subject: Re: Re: [SQL] renaming columns... danger? In-Reply-To: <20010107151538U.t-ishii@sra.co.jp> References: <20010107151215W.t-ishii@sra.co.jp> <20001027050141.76502.qmail@web10004.mail.yahoo.com> <20010107151215W.t-ishii@sra.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200101/152 X-Sequence-Number: 2824 At 15:15 7/01/01 +0900, Tatsuo Ishii wrote: >> As for the latest CVS source, it looks still we have problems >> regarding alter table rename column and pg_dump as Grant has >> mentioned. Results of pg_dump is attached. > >Sorry, an attachmet was missing. > I can reproduce this in 7.0.2 as well; it's because the PK attr name comes from the index relation attr names, not the original relation. I'll look into alternative queries but would welcome suggestions. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/