Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 76CF6475FB8; Mon, 4 Mar 2002 15:47:52 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g24KlqS07686; Mon, 4 Mar 2002 15:47:52 -0500 (EST) To: dan@langille.org Cc: pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: Uniqueness of rule, constraint, and trigger names In-reply-to: <200203042043.g24Khek80028@lists.unixathome.org> References: <200203042004.g24K4lk79699@lists.unixathome.org> <200203042043.g24Khek80028@lists.unixathome.org> Comments: In-reply-to "Dan Langille" message dated "Mon, 04 Mar 2002 15:43:38 -0500" Date: Mon, 04 Mar 2002 15:47:52 -0500 Message-ID: <7683.1015274872@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/43 X-Sequence-Number: 6925 "Dan Langille" writes: > It would be easily detected at load time. Then you direct the user to the > tool mentioned above. But if the user has already dumped and flushed his old installation, he's still in need of a time machine. Hmm, maybe what we need is a tool that can be applied during load. Essentially, alter incoming constraint names as needed to make them unique. We could have this enabled by a SET switch... regards, tom lane