Re: Information Schema and constraint names not unique

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Information Schema and constraint names not unique
Date: 2003-11-06 16:37:32
Message-ID: Pine.LNX.4.44.0311061732450.29650-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-11-06 16:42:13 Re: Information Schema and constraint names not unique
Previous Message Tom Lane 2003-11-06 15:54:29 Re: Information Schema and constraint names not unique