Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 28A7147619E; Mon, 4 Mar 2002 15:38:35 -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 g24KcMS07584; Mon, 4 Mar 2002 15:38:22 -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: <200203042004.g24K4lk79699@lists.unixathome.org> References: <200203042004.g24K4lk79699@lists.unixathome.org> Comments: In-reply-to "Dan Langille" message dated "Mon, 04 Mar 2002 15:04:45 -0500" Date: Mon, 04 Mar 2002 15:38:22 -0500 Message-ID: <7581.1015274302@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/45 X-Sequence-Number: 6927 "Dan Langille" writes: > On 4 Mar 2002 at 14:24, Tom Lane wrote: >> ... but I'm a little worried about the possibility of errors >> in loading schemas from existing databases, where there might be >> non-unique constraint names. > Create a tool to generate unique constraint names during a dump. And then all we need is a time machine, so we can make existing instances of pg_dump contain the tool? It's not that easy ... I am not sure that there's really a problem here, because I don't think duplicate constraint names will be generated during plain CREATE operations. However, an ALTER TABLE might leave you with a problem. Hard to tell if this is critical enough to worry about. regards, tom lane