From: Rod Taylor <rbt@zort.ca>
To: dan@langille.org
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Uniqueness of rule, constraint, and trigger names
Date: Mon, 4 Mar 2002 16:40:16 -0500
Message-ID: <00f801c1c3c5$b00d7490$b002000a@jester> (raw)
References: <200203042004.g24K4lk79699@lists.unixathome.org>
<7581.1015274302@sss.pgh.pa.us>
If pgupgrade can be fixed to work, perhaps it could set off warnings
on items that need to be corrected in a 'schema upgradability test'
which will ensure that the user can upgrade it properly -- it
shouldn't upgrade if it can't guarentee an upgrade will succeed.
This should include full schema test (that whole bad schema entry
stuff that pg_dump is supposed to work around) too.
Something I'm thinking about digging into.
--
Rod Taylor
This message represents the official view of the voices in my head
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: <dan@langille.org>
Cc: <pgsql-hackers@postgreSQL.org>; <pgsql-sql@postgreSQL.org>
Sent: Monday, March 04, 2002 3:38 PM
Subject: Re: [HACKERS] [SQL] Uniqueness of rule, constraint, and
trigger names
> "Dan Langille" <dan@langille.org> 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
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: rbt@zort.ca, dan@langille.org, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Uniqueness of rule, constraint, and trigger names
In-Reply-To: <00f801c1c3c5$b00d7490$b002000a@jester>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox