Re: Information Schema and constraint names not unique - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Information Schema and constraint names not unique
Date
Msg-id Pine.LNX.4.44.0311061732450.29650-100000@peter.localdomain
Whole thread Raw
In response to Re: Information Schema and constraint names not unique  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Information Schema and constraint names not unique  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> > Would a good halfway house be to ensure that generated names were unique
> > within a schema (e.g. instead of generating "$1" generate
> > "tablename$1")?
>
> No, because that buys into all of the serialization and deadlocking
> problems that doing it the spec's way entail

I don't think we really need a method to guarantee unique names.  It would
already help a lot if we just added the table name, or something that was
until a short time before the action believed to be the table name, or
even only the table OID, before (or after) the $1.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Information Schema and constraint names not unique
Next
From: Tom Lane
Date:
Subject: Re: Information Schema and constraint names not unique