--- Tom Lane wrote:
> I wrote:
> > Patrick Samson writes:
> >> - Add the same filter in the build of TG_relatts.
> >> This will prevent a tcl script which loops on
> >> TG_relattrs to fail in trying to use a dropped
> >> column.
> > This is deliberately *not* done in 7.4, because it
> would break the
> > documented behavior of TG_relatts:
> I thought of a good compromise solution: instead of
> putting the dropped
> columns' names into TG_relatts, we can put
> empty-string list elements.
> This preserves the attnum correspondence, and
> anything that iterates
> over TG_relatts should be coded to ignore empty
> elements anyway, no?

OK, I didn't pay attention to the numbering concern.
Your compromise suits me. I prefer to filter on
empty strings than on something with some dots in it.
Or to run an spi_exec to test the attisdropped.

Tom, your suggestion to look in OLD or NEW for live
columns may be cover all situations. I use a code
(not mine, but I try to make it run on Cygwin) that
use a NULL value if [info exists NEW($field)] is

Many thanks to all.

Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to