Re: No longer possible to query catalogs for index capabilities? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: No longer possible to query catalogs for index capabilities?
Date
Msg-id CACjxUsM0xQ2A7dtH3jAp2sD1qYWvTPPAJLfNF3kYQ9i-bznF0w@mail.gmail.com
Whole thread Raw
In response to Re: No longer possible to query catalogs for index capabilities?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: No longer possible to query catalogs for index capabilities?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Aug 10, 2016 at 12:31 PM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:

> These could be limited to being testable only on a specified index, and
> not AM-wide:

>   predicate_locks (? maybe)

That one seems like it should either be at the AM level or not
included at all.  Where it would be interesting to know is if you
are a hacker looking for an AM to enhance with support, or (when
there is more than just btree supported, so it is not so easy to
remember) if you are a DBA investigating a high rate of
serialization failures and want to know whether indexes of a
certain type have index-relation predicate locking granularity or
something more fine-grained.  The latter use case seems plausible
once there is more of a mix of support among the AMs.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?
Next
From: Claudio Freire
Date:
Subject: Re: Heap WARM Tuples - Design Draft