Postgres Pro
Downloads
Home   >   mailing lists

Exposing index AM properties at SQL level - Mailing list pgsql-hackers

From Egor Rogov
Subject Exposing index AM properties at SQL level
Date
Msg-id 288c944d-653e-81d8-d2d7-7434f754b148@postgrespro.ru
Whole thread Raw
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

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