Re: generic plans and "initial" pruning

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: generic plans and "initial" pruning
Date: 2022-01-18 01:32:57
Message-ID: CA+HiwqHzXBhXX=dKxJ-z9Kpz3Aazc-9R9awAZnMYkoPaybRDEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 14, 2022 at 11:10 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> On Thu, Jan 6, 2022 at 3:45 PM Amul Sul <sulamul(at)gmail(dot)com> wrote:
> > Here are few comments for v1 patch:
>
> Thanks Amul. I'm thinking about Robert's latest comments addressing
> which may need some rethinking of this whole design, but I decided to
> post a v2 taking care of your comments.

cfbot tells me there is an unused variable warning, which is fixed in
the attached v3.

--
Amit Langote
EDB: http://www.enterprisedb.com

Attachment Content-Type Size
v3-0001-Teach-AcquireExecutorLocks-to-acquire-fewer-locks.patch application/octet-stream 46.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-01-18 01:36:04 Re: Refactoring of compression options in pg_basebackup
Previous Message Peter Smith 2022-01-18 01:26:38 Re: row filtering for logical replication