Re: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare()

From: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>
Subject: Re: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare()
Date: 2020-11-02 17:45:37
Message-ID: 160433913709.4948.8203602749014580737.pgcf@coridan.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Status update for a commitfest entry.

This thread was inactive for a while. The latest review suggests that it is Ready For Committer.
I also took a quick look at the patch and agree that it looks sensible. Maybe add a comment before the _bt_compare_inl() to explain the need for this code change.

The new status of this patch is: Ready for Committer

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-11-02 17:51:39 Re: Collation versioning
Previous Message Heikki Linnakangas 2020-11-02 17:43:38 Re: Split copy.c