Re: WIP: Covering + unique indexes. - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: WIP: Covering + unique indexes.
Date
Msg-id CAH2-Wz=Zf70fUPco1RhtELAAJ=wOe6BhVjGNsyTn1pZ3XocJqw@mail.gmail.com
Whole thread Raw
In response to Re: WIP: Covering + unique indexes.  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: WIP: Covering + unique indexes.
List pgsql-hackers
On Wed, Apr 18, 2018 at 10:47 PM, Teodor Sigaev <teodor@sigaev.ru> wrote:
> Thank you, pushed.

Thanks.

I saw another preexisting issue, this time one that has been around
since 2007. Commit bc292937 forgot to remove a comment above
_bt_insertonpg() (the 'afteritem' stuff ended up being moved to the
bottom of _bt_findinsertloc(), where it remains today). The attached
patch fixes this, and in passing mentions the fact that
_bt_insertonpg() only performs retail insertions, and specifically
never inserts high key items.

I don't think it's necessary to add something about negative infinity
items to the same comment block. While it's true that _bt_insertonpg()
cannot truncate downlinks to make new minus infinity items, I see that
as a narrower issue.

-- 
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Is there a memory leak in commit 8561e48?
Next
From: Andres Freund
Date:
Subject: Re: Excessive PostmasterIsAlive calls slow down WAL redo