Re: executor relation handling - Mailing list pgsql-hackers

From David Rowley
Subject Re: executor relation handling
Date
Msg-id CAKJS1f8cYQP64jsNU1-vLmE9Z1mCx_+0zjCgA_kCWfddmcLz_w@mail.gmail.com
Whole thread Raw
In response to Re: executor relation handling  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: executor relation handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 1 October 2018 at 19:39, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
> For this and the other cases (AcquireRewriteLocks, AcquireExecutorLocks,
> etc.), I wonder whether we couldn't just *not* recalculate the lock mode
> based on inspecting the query tree to cross-check with rellockmode?  Why
> not just use rellockmode for locking?  Maybe, okay to keep doing that in
> debug builds though.  Also, are the discrepancies like this to be
> considered bugs of the existing logic?

I got the impression Tom was just leaving that in for a while to let
the buildfarm verify the new code is getting the same lock level as
the old code. Of course, I might be wrong.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: has_column_privilege behavior (was Re: Assert failed insnprintf.c)
Next
From: Stephen Frost
Date:
Subject: Re: has_column_privilege behavior (was Re: Assert failed insnprintf.c)