Re: attisdropped, * expansion and tg_trigtuple

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: attisdropped, * expansion and tg_trigtuple
Date: 2003-06-19 14:00:06
Message-ID: 8337.1056031206@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> 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?

Given recent discussions about decoupling logical and physical column
order, I'd think that assumption might blow up in your face in a version
or two. It's unsafe even today if the relation has dropped columns.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nigel J. Andrews 2003-06-19 14:01:38 Re: why are my SELECTs in transaction?
Previous Message Tom Lane 2003-06-19 13:56:03 Re: explicit joins vs implicit joins