Exposing index AM properties at SQL level

From: Egor Rogov <e(dot)rogov(at)postgrespro(dot)ru>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Exposing index AM properties at SQL level
Date: 2024-12-08 12:51:32
Message-ID: 288c944d-653e-81d8-d2d7-7434f754b148@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I wonder if there is some hidden logic behind exposing (or not exposing)
index AM properties at SQL level?

For example, should newly added amcanbuildparallel (b437571) be
available via pg_indexam_has_property()? And also other boolean
properties like ampredlocks or amusemaintenanceworkmem? I can't see a
particular practical reason to expose them, but it looks inconsistently.

Thanks,
Egor

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2024-12-08 12:53:21 Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?
Previous Message Andrei Lepikhov 2024-12-08 08:44:23 Re: Do not scan index in right table if condition for left join evaluates to false using columns in left table