| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Prajval Poojari <ppoojari(at)erwin(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14601: Alternative support for amcanorder column under pg_am |
| Date: | 2017-03-28 20:40:48 |
| Message-ID: | CAKFQuwaqZT360BHg9jQUwRN27mwXoEOfzsj=0i-6Pm=jm_wteQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Mar 28, 2017 at 1:32 PM, Prajval Poojari <ppoojari(at)erwin(dot)com> wrote:
> Yes David I agree
> But the problem occurring is column named amcanorder which was available
> until 9.5 release is not available in 9.6
> So do we have any alternative solution if I want to use that column in 9.6
> ?
>
You agree with what?
The table mentioned in the page I linked to has this:
pg_indexam_has_property(am_oid, prop_name) boolean test whether an index
access method has a specified property
Definitions of am_oid and prop_name and present later on the same page.
Whatever it is you are doing will need version detection logic and a
different query for the newer stuff versus the older stuff.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2017-03-28 20:48:34 | Re: BUG #14601: Alternative support for amcanorder column under pg_am |
| Previous Message | Tom Lane | 2017-03-28 20:32:44 | Re: postmaster became multithreaded |