Re: Index AmInsert Parameter Confused? - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Index AmInsert Parameter Confused?
Date
Msg-id CAEze2Wi2FO3ZZiMPPUYA8k7C=Rf9+Con3kK3h=yMPnZ_tv52JA@mail.gmail.com
Whole thread Raw
In response to Index AmInsert Parameter Confused?  (jacktby jacktby <jacktby@gmail.com>)
Responses Re: Index AmInsert Parameter Confused?
List pgsql-hackers
On Tue, 26 Sept 2023 at 18:38, jacktby jacktby <jacktby@gmail.com> wrote:
>
> typedef bool (*aminsert_function) (Relation indexRelation,
>   Datum *values,
>   bool *isnull,
>   ItemPointer heap_tid,
>   Relation heapRelation,
>   IndexUniqueCheck checkUnique,
>   bool indexUnchanged,
>   struct IndexInfo *indexInfo);
>
> Why is there a heap_tid, We haven’t inserted the value, so where does it from ?

Index insertion only happens after the TableAM tuple has been
inserted. As indexes refer to locations in the heap, this TID contains
the TID of the table tuple that contains the indexed values, so that
the index knows which tuple to refer to.

Note that access/amapi.h describes only index AM APIs; it does not
cover the table AM APIs descibed in access/tableam.h

Kind regards,

Matthias van de Meent



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: False "pg_serial": apparent wraparound” in logs
Next
From: Jeff Davis
Date:
Subject: Re: Questions about the new subscription parameter: password_required