X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D7934D1B4F8 for ; Thu, 23 Oct 2003 01:47:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 40144-01 for ; Wed, 22 Oct 2003 22:46:50 -0300 (ADT) Received: from necsin-fw.nec.com.sg (necsin-fw.nec.com.sg [203.127.255.1]) by svr1.postgresql.org (Postfix) with ESMTP id 4E502D1B525 for ; Wed, 22 Oct 2003 22:46:41 -0300 (ADT) Received: from kato.nec.com.sg (kato.nec.com.sg [203.127.254.2]) by necsin-fw.nec.com.sg with ESMTP id h9N1kUh0004227 for ; Thu, 23 Oct 2003 09:46:33 +0800 (SGT) Received: from necsind1.nec.com.sg ([203.127.252.220]) by kato.nec.com.sg with ESMTP id h9N1kUJT002674 for ; Thu, 23 Oct 2003 09:46:30 +0800 (SGT) Subject: Re: Postgresql performance To: pgsql-performance@postgresql.org X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: CHEWTC@ap.nec.com.sg Date: Thu, 23 Oct 2003 09:46:32 +0800 X-MIMETrack: Serialize by Router on NECSIND1/WTC/NECSIN(Release 5.0.12 |February 13, 2003) at 10/23/2003 09:46:33 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.7 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME, QUOTED_EMAIL_TEXT X-Spam-Level: X-Archive-Number: 200310/592 X-Sequence-Number: 4340 Hi The Postgresql package came from the Redhat v9.0 CDROM. I have checked the version using psql --version and it showed v7.3.2 How to check the pg_dump version? Thank you, REgards. Josh Berkus cc: Subject: Re: [PERFORM] Postgresql performance 23/10/2003 12:06 AM NEC, > After a few weeks of usage, when we do a \d at the sql prompt, there was a > duplicate object name, ie it can be a duplicate row of index or table. > When we do a \d table_name, it will show a duplication of column names > inside the table. I think the version of PSQL and pg_dump which you are using do not match the back-end database version. Correct this. -- Josh Berkus Aglio Database Solutions San Francisco