Re: ALTER TABLE RENAME fix

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Brent Verner <brent(at)rcfile(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: ALTER TABLE RENAME fix
Date: 2001-11-13 01:32:51
Message-ID: 29681.1005615171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Good question. Several people thought attno was the way to go and it
> seemed more natural because almost everything else goes by attno and not
> name.

Since the primary key for pg_attribute is reloid+attnum, it would seem
that that's an appropriate representation for RI trigger links too.

But Hiroshi's got a point: we have a whole set of issues with tracking
object dependencies, and it probably makes sense to think about how we
are going to deal with those issues before we fool around with changing
the representation of RI triggers.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2001-11-13 01:37:46 Re: Possible patch to remove "triggered data change" support
Previous Message Bruce Momjian 2001-11-13 01:30:39 Re: Possible patch to remove "triggered data change" support