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 8e2dbb701001091253w6b45e189r48fd0b107dc9d64a@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>:
>> OK, I admit that I'm totally new that area of code, so I'm not seeing
>> it - what does it break?
>
> The main problem is...

Ah OK. Thanks for the explanation.

> 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.

Cheers,
Dean


pgsql-hackers by date:

Previous
From: Marcin Mańk
Date:
Subject: Re: synchronized snapshots
Next
From: Roger Leigh
Date:
Subject: Re: Add .gitignore files to CVS?