Received: from success.vitalect.com (ns1.vitalect.com [208.184.226.140])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f175Ujx88501;
	Wed, 7 Feb 2001 00:30:45 -0500 (EST)
	(envelope-from thyaga@vitalect.com)
Received: from bytekinc.com (success.vitalect.com [192.168.1.2])
	by success.vitalect.com (8.9.3/8.9.3) with ESMTP id VAA11032;
	Tue, 6 Feb 2001 21:30:41 -0800
Message-ID: <3A80DD84.B76AFB44@bytekinc.com>
Date: Tue, 06 Feb 2001 21:30:44 -0800
From: Thyagarajan Vasudevan <thyaga@vitalect.com>
Organization: ByteK Designs, Inc.
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: pgsql-admin@postgresql.org, pgsql-general@postgresql.org
Subject: pg_upgrade
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200102/52
X-Sequence-Number: 652

Hi All
    I am trying to upgrade from Postgres 6.5 to Postgres 7.0.3. Now, in
the previous version of the Database, i have a lot of triggers which
simulate the Foreign key functionality, by using the checkPrimaryKey and
the checkForeignKey functions defined in refint.c.
    My question is:
        If I use pg_upgrade to shift from 6.5 to 7.0.3, will these
triggers automatically be removed and be converted into a FOREIGN KEY
constraint in the appropriate tables.

Thanks
Thyaga