Re: Incremental sort for access method with ordered scan support (amcanorderbyop)

From: Miroslav Bendik <miroslav(dot)bendik(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Incremental sort for access method with ordered scan support (amcanorderbyop)
Date: 2023-04-20 13:36:52
Message-ID: CAPoEpV2O04MZSvyeXZ1cfvj1Ra_zWOVvGkVTCyxxzTHno8QjGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I've just pushed a fix to master for this. See [1]. If you base your
> patch atop of that you should be able to list list_copy_head() without
> any issues.

Thanks for this fix. Now the version
am_orderbyop_incremental_sort_v3.1.patch [1] works without issues
using the master branch.

[1] https://www.postgresql.org/message-id/attachment/146450/am_orderbyop_incremental_sort_v3.1.patch

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-04-20 15:06:52 Re: pgsql: Further cleanup of autoconf output files for GSSAPI changes.
Previous Message Ashutosh Bapat 2023-04-20 13:31:49 memory context mismatch in LockMethodLocalHash entries.