Re: [HACKERS] Regarding B-Tree Lookup - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Regarding B-Tree Lookup
Date
Msg-id CAB7nPqQsDsv=y3gxoeMK0s68-Rb2w__3CA+0iC6esOWmzXB+JA@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Regarding B-Tree Lookup  (Mahi Gurram <teckymahi@gmail.com>)
Responses Re: [HACKERS] Regarding B-Tree Lookup
Re: [HACKERS] Regarding B-Tree Lookup
List pgsql-hackers
On Tue, May 2, 2017 at 6:12 PM, Mahi Gurram <teckymahi@gmail.com> wrote:
> I'm building some custom extension on top of postgres 9.6.1. As part of
> that, I would like to read Heap Tuple directly from my extension using
> Primary Key.
>
> By default, postgres table index(B-Tree) its PrimaryKey(PK). So, i would
> like to get TID by doing a lookup into PK's B-Tree index. Using which i
> could read HeapTuple directly.
>
> Please suggest me the easiest way to lookup into PK's B-Tree index for
> getting TIDs.

Why don't you just use SPI within your extension? No need to copy the
logic for btree lookups this way.
https://www.postgresql.org/docs/9.6/static/spi.html

> Suggesting a postgres extensions which does B-Tree lookup will also helps
> me.

contrib/amcheck looks at raw btree data, though I am not sure that you
actually need to go down to that. But that's hard to reach a
conclusion without more details.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [Proposal]: Extends VisualStudio to automaticallyprecompile EmbeddedSQL
Next
From: hariprasath nallasamy
Date:
Subject: [HACKERS] Shared Memory hash tables only at startup