Re: Index AM API cleanup

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Index AM API cleanup
Date: 2024-09-24 08:50:32
Message-ID: 8cf2db1e-8d68-4d0a-8b9a-055c2d00f4f1@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Next, I have reviewed patches

v17-0010-Track-sort-direction-in-SortGroupClause.patch
v17-0011-Track-scan-reversals-in-MergeJoin.patch

Both of these seem ok and sensible to me.

They take the concept of the "reverse" flag that already exists in the
affected code and just apply it more consistently throughout the various
code layers, instead of relying on strategy numbers as intermediate
storage. This is both helpful for your ultimate goal in this patch
series, and it also makes the affected code areas simpler and more
consistent and robust.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-09-24 09:04:31 Re: not null constraints, again
Previous Message Dmitry Dolgov 2024-09-24 08:39:45 Re: Add llvm version into the version string