Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)googlemail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function
Date: 2010-01-10 17:57:44
Message-ID: 7758.1263146264@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dean Rasheed <dean(dot)a(dot)rasheed(at)googlemail(dot)com> writes:
> 2010/1/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> I think that a variant of your idea could be made to work: change
>> plpgsql_LookupIdentifiers to a three-state variable (which'd basically
>> mean "in DECLARE, in a SQL expression, anywhere else"), do no lookups in
>> DECLARE, and in SQL expressions do lookups but never throw any errors.
>> I'll have a go at that.

> Sounds plausible.

I've applied a patch along these lines.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2010-01-10 17:58:00 Re: pgsql: Also update ChangerLog file.
Previous Message Peter Eisentraut 2010-01-10 17:55:28 Re: RADIUS authentication