Re: generic plans and "initial" pruning

From: Zhihong Yu <zyu(at)yugabyte(dot)com>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: generic plans and "initial" pruning
Date: 2022-03-11 22:09:16
Message-ID: CALNJ-vTt0pY9MP04Ewew+qTysNddUJOyACT6UrXx4BUaKJSJQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
w.r.t. v5-0003-Teach-AcquireExecutorLocks-to-skip-locking-pruned.patch :

(pruning steps containing expressions that can be computed before
before the executor proper has started)

the word 'before' was repeated.

For ExecInitParallelPlan():

+ char *execlockrelsinfo_data;
+ char *execlockrelsinfo_space;

the content of execlockrelsinfo_data is copied into execlockrelsinfo_space.
I wonder if having one of execlockrelsinfo_data and
execlockrelsinfo_space suffices.

Cheers

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2022-03-11 22:46:59 Re: role self-revocation
Previous Message Justin Pryzby 2022-03-11 21:49:00 Re: wal_compression=zstd