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

From Tom Lane
Subject Re: No longer possible to query catalogs for index capabilities?
Date
Msg-id 8957.1469474359@sss.pgh.pa.us
Whole thread Raw
In response to Re: No longer possible to query catalogs for index capabilities?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: No longer possible to query catalogs for index capabilities?  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Re: No longer possible to query catalogs for index capabilities?  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jul 25, 2016 at 10:35 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> You missed the "compelling argument why it's needed" part.  What is the
>> need for this?

> It's self-evident that this thread wouldn't exist if it were not the
> case that people had queries that no longer work because of these new
> changes.  You can hold your breath and pretend that every single one
> of those queries is probably misdesigned, but I do not think anyone
> else will find that argument convincing.

We've already broken existing queries against pg_am, simply because the
columns are not there anymore; and that decision is not getting undone
at this point.  I'm willing to consider putting back some substitute
capability, but I'd like to see as much evidence for adding that as we'd
expect for any other new feature.  Andrew still hasn't shown a concrete
example of what he needs to do and why.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Curing plpgsql's memory leaks for statement-lifespan values
Next
From: Andrew Gierth
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?