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

From Dean Rasheed
Subject Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function
Date
Msg-id 8e2dbb701001091209o16aae16bs6af3a075d00e223b@mail.gmail.com
Whole thread Raw
In response to Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2010/1/9 Tom Lane <tgl@sss.pgh.pa.us>:
> Dean Rasheed <dean.a.rasheed@googlemail.com> writes:
>> I wonder if it might be better to have plpgsql_parse_dblword() ignore
>> plpgsql_LookupIdentifiers, and always do the lookups.
>
> Not if you'd like things to still work.
>

OK, I admit that I'm totally new that area of code, so I'm not seeing
it - what does it break?
[regression tests still pass BTW]

Regards,
Dean


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function
Next
From: Tom Lane
Date:
Subject: Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function