| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | SQL access to access method details |
| Date: | 2016-03-28 20:02:44 |
| Message-ID: | 56F98DE4.2090000@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
While working on a tool to capture catalog/stats info and looking at
cross version compatibility, I noticed that the pg_am changes removed
SQL access to a bunch of AM info. [1] indicates that's part of the
purpose of the patch; are we sure no tools are using this info? Unlike
previous catalog compatibility breaks, this one completely removes that
information, so if someone was using it they're now completely hosed.
[1] http://www.postgresql.org/message-id/55FEC1AB.8010406@2ndquadrant.com
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-28 20:27:02 | Re: Dealing with collation and strcoll/strxfrm/etc |
| Previous Message | Stephen Frost | 2016-03-28 19:36:54 | Re: Dealing with collation and strcoll/strxfrm/etc |