Re: itemptr_encode/itemptr_decode - Mailing list pgsql-hackers

From Andres Freund
Subject Re: itemptr_encode/itemptr_decode
Date
Msg-id 20190417231442.6qxcyiprlq3ybkcm@alap3.anarazel.de
Whole thread Raw
In response to itemptr_encode/itemptr_decode  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: itemptr_encode/itemptr_decode
List pgsql-hackers
Hi,

On 2019-04-17 18:57:00 -0400, Tom Lane wrote:
> What on God's green earth are these functions doing in
> src/include/catalog/index.h?

> They don't have any obvious connection to indexes, let alone
> catalog operations on indexes, which is what that file is for.

Well, they were previously declared & defined in
src/backend/catalog/index.c - that's where the location is coming from
(and where they still are defined). And they're currently only used to
implement the index validation scans, which requires the validation scan
to decode item pointers stored in the tuplesort presented to it.

I'm happy to move them elsewhere, but I'm not sure there's really a good
location. I guess we could move them to itemptr.h - but they're not
really something particularly generally usable.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: itemptr_encode/itemptr_decode
Next
From: Tom Lane
Date:
Subject: Re: itemptr_encode/itemptr_decode