Re: heapgettup refactoring

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: heapgettup refactoring
Date: 2023-01-18 11:04:15
Message-ID: 789c6762-1412-d0cc-4faa-66c1ee7f8ef0@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10.01.23 21:31, Melanie Plageman wrote:
> On Thu, Jan 5, 2023 at 8:52 AM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>
>> Ok, let's look through these patches starting from the top then.
>>
>> v4-0001-Add-no-movement-scan-helper.patch
>>
>> This makes sense overall; there is clearly some duplicate code that can
>> be unified.
>>
>> It appears that during your rebasing you have effectively reverted your
>> earlier changes that have been committed as
>> 8e1db29cdbbd218ab6ba53eea56624553c3bef8c. You should undo that.
>
> Thanks. I think I have addressed this.
> I've attached a rebased v5.

In your v2 patch, you remove these assertions:

- /* check that rs_cindex is in sync */
- Assert(scan->rs_cindex < scan->rs_ntuples);
- Assert(lineoff == scan->rs_vistuples[scan->rs_cindex]);

Is that intentional?

I don't see any explanation, or some other equivalent code appearing
elsewhere to replace this.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2023-01-18 11:06:34 Re: postgres_fdw: commit remote (sub)transactions in parallel during pre-commit
Previous Message Dean Rasheed 2023-01-18 10:52:24 Re: Add proper planner support for ORDER BY / DISTINCT aggregates