Re: GIN pageinspect support for entry tree and posting tree

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Roman Khapov <rkhapov(at)yandex-team(dot)ru>
Subject: Re: GIN pageinspect support for entry tree and posting tree
Date: 2026-01-06 16:44:54
Message-ID: CALdSSPh4017iHiHTDuNkjvVVNS==xKMQ2Kb=p=N4FLCawpfhqA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 6 Jan 2026 at 21:28, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>
> On Mon, 5 Jan 2026 at 13:39, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> >
> >
> >
> > > On 4 Jan 2026, at 00:25, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
> > >
> > > PFA v6
> >
> > Would it be theoretically possible to unite functions for different GIN page types?
> > e.g. merge gin_entrypage_items + gin_datapage_items -> gin_tree_items? Or is it an awkward API?
>
> For this, I borrowed this design from HASH and BRIN pageinspect
> implementation. For them, we have one function-per-page-type. So,
> maybe we can have dynamic schema here, but I don't see this as an
> improvement to design.
>
> --
> Best regards,
> Kirill Reshke

CF bot did like trailing whitespace in regression output files,
posting v8 with this issue fixed.

--
Best regards,
Kirill Reshke

Attachment Content-Type Size
v8-0001-GIN-pageinspect-support-for-entry-tree-and-postin.patch application/octet-stream 29.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-01-06 16:46:37 Re: Periodic authorization expiration checks using GoAway message
Previous Message Jacob Champion 2026-01-06 16:41:54 Re: Periodic authorization expiration checks using GoAway message