Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vinay Banakar <vinay(dot)s(dot)banakar(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg
Date: 2019-09-13 04:29:17
Message-ID: 23378.1568348957@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Vinay Banakar <vinay(dot)s(dot)banakar(at)gmail(dot)com> writes:
> Thank you for finding the root cause, I just checked on 9.15.17 and it is
> still failing here also.
> But I distinctly remember it working earlier, not sure which version of pg
> (at least <9.5.16) though as I have lost that earlier setup.

Oh! I misread your report as being that it worked on 9.5.x and failed
on 9.6.x. If it really did work on some earlier 9.5.x version, then
we must've busted it with a patch ... but what? That bizarre code in
ExecEvalWholeRowVar is much older than 9.5 (looks like it dates to
8e617e29a), and the mistake proper goes back to the introduction of
WITH CHECK OPTION in 9.4 (4cbe3ac3e). I'm not seeing any other
moving parts here.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-09-13 06:06:52 BUG #16008: pgrouting rpm missing in pgdg
Previous Message Zollinger Beat (OIZ) 2019-09-13 04:20:06 AW: BUG #16004: New Version pgrouting_96-2.6.3-1 has dependency to postgis25_96 in postgresql.org-Channel