attisdropped, * expansion and tg_trigtuple - Mailing list pgsql-general

From Nigel J. Andrews
Subject attisdropped, * expansion and tg_trigtuple
Date
Msg-id Pine.LNX.4.21.0306191034410.29248-100000@ponder.fairway2k.co.uk
Whole thread Raw
Responses Re: attisdropped, * expansion and tg_trigtuple  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

In light of the recent discussion on * expansion and how dropped columns impact
on record and rowtype variables in plpgsql I thought I'd see if anyone knows of
hand the answer to:

If in a trigger one does a select * from the table the trigger is on is it safe
to assume that tg_trigtuple (and so tg_newtuple) will use the same TupleDesc as
that returned from the select *, i.e. the tg_relation->rd_att TupleDesc?

As I say, just thought I'd ask before I add code to my trigger to map one to
the other via attribute name not number.


--
Nigel J. Andrews


pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Incremental backups, and backup history
Next
From: "Shridhar Daithankar"
Date:
Subject: Re: Incremental backups, and backup history