Re: No longer possible to query catalogs for index capabilities?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Kevin Grittner <kgrittn(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: No longer possible to query catalogs for index capabilities?
Date: 2016-08-11 18:20:17
Message-ID: 62a0799e-27d3-6676-23a6-e5637cc5bc43@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/11/2016 10:46 AM, Kevin Grittner wrote:
> On Wed, Aug 10, 2016 at 5:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Kevin Grittner <kgrittn(at)gmail(dot)com> writes:

> But a DBA who has a problem doesn't care what the truth will be in
> a year or two -- the interest is in *right now* on one particular
> cluster.
>
>> If you are a DBA wanting to know how fine-grained the locking is
>> in a particular index type, you really need to read the source code
>> or ask a hacker.
>

This has to be a joke. With the greatest respect, this show a world of
disconnect from the people that actually use this software.

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-11 18:32:59 Allowing GIN array_ops to work on anyarray
Previous Message Robert Haas 2016-08-11 18:19:41 Re: LWLocks in DSM memory