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:09:22
Message-ID: 8e2dbb701001091209o16aae16bs6af3a075d00e223b@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>:
> Dean Rasheed <dean(dot)a(dot)rasheed(at)googlemail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-09 20:28:11 Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function
Previous Message Tom Lane 2010-01-09 19:54:14 Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function