Re: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare() - Mailing list pgsql-hackers

From Anastasia Lubennikova
Subject Re: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare()
Date
Msg-id 160433913709.4948.8203602749014580737.pgcf@coridan.postgresql.org
Whole thread Raw
In response to Re: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare()  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: RE: Delaying/avoiding BTreeTupleGetNAtts() call within _bt_compare()  (Peter Geoghegan <pg@bowt.ie>)
List 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

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Split copy.c
Next
From: Tom Lane
Date:
Subject: Re: Collation versioning