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

From Bruce Momjian
Subject Re: No longer possible to query catalogs for index capabilities?
Date
Msg-id 20160806151328.GH26927@momjian.us
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?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Sat, Aug  6, 2016 at 04:04:41PM +0100, Andrew Gierth wrote:
> >>>>> "Bruce" == Bruce Momjian <bruce@momjian.us> writes:
> 
>  Bruce> Would it be helpful to output an array of strings representing
>  Bruce> the index definition?
> 
>  >> Why would that help, if the point is to enable programmatic access
>  >> to information?
> 
>  Bruce> I was thinking an array of strings would avoid problems in
>  Bruce> having to re-scan the output for tokens.
> 
> OK, but that still leaves the issue of how to interpret each string,
> yes?

Yes, you still have to parse it, just not scan/tokenize it.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+                     Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?
Next
From: Tom Lane
Date:
Subject: Re: Possible duplicate release of buffer lock.