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

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

2010/1/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Roger Leigh 2010-01-09 20:57:56 Re: Add .gitignore files to CVS?
Previous Message Marcin Mańk 2010-01-09 20:44:38 Re: synchronized snapshots