RI triggers and schemas - Mailing list pgsql-hackers

From Tom Lane
Subject RI triggers and schemas
Date
Msg-id 8615.1017174728@sss.pgh.pa.us
Whole thread Raw
Responses Re: RI triggers and schemas  (Jan Wieck <janwieck@yahoo.com>)
Re: RI triggers and schemas  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-hackers
As of CVS tip, referential integrity triggers are kinda broken: they
will only work for tablenames that are in the current search path.
I think that instead of storing just table names in the trigger
parameters, we should store either table OIDs or schema name + table
name.  Do you have any preferences about this?

An advantage of using OIDs is that we could forget the pushups that
ALTER TABLE RENAME presently goes through to update RI triggers.

On the other hand, as long as the RI implementation depends on
generating textual queries, it'd be faster to have the names available
than to have to look them up from the OID.  But I seem to recall Stephan
threatening to rewrite that code at a lower level pretty soon, so the
speed issue might go away.  In any case it's probably a minor issue
compared to generating the query plan.

So I'm leaning towards OIDs, but wanted to see if anyone had a beef
with that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: GB Clark
Date:
Subject: Re: Autoconf upgrade
Next
From: Tom Lane
Date:
Subject: Indexes, TOAST tables, and namespaces