| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org, Rod Taylor <rbt(at)zort(dot)ca> |
| Subject: | Re: Scope of constraint names |
| Date: | 2002-07-07 21:55:25 |
| Message-ID: | Pine.LNX.4.44.0207072313440.930-100000@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> A considerable advantage of per-relation constraint names is that a new
> unique name can be assigned for a nameless constraint while holding only
> a lock on the target relation. We'd need a global lock to create unique
> constraint names in the SQL92 semantics.
Presumably, the field pg_class.relchecks already keeps a count of the
number of constraints, so it should be possible to assign numbers easily.
> The only way I can see around that would be to use newoid(), or perhaps
> a dedicated sequence generator, to construct constraint names. The
> resulting unpredictable constraint names would be horribly messy to deal
> with in the regression tests, so I'm not eager to do this.
Or we simply assign constraint names explicitly in the regression tests.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-07 23:29:30 | Re: CLUSTER not lose indexes |
| Previous Message | Peter Eisentraut | 2002-07-07 21:54:42 | Re: Proposal: CREATE CONVERSION |