Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function
Date
Msg-id 7758.1263146264@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function  (Dean Rasheed <dean.a.rasheed@googlemail.com>)
Responses Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function  (Dean Rasheed <dean.a.rasheed@googlemail.com>)
List pgsql-hackers
Dean Rasheed <dean.a.rasheed@googlemail.com> writes:
> 2010/1/9 Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: RADIUS authentication
Next
From: Magnus Hagander
Date:
Subject: Re: RADIUS authentication