| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL access to access method details |
| Date: | 2016-03-30 08:53:25 |
| Message-ID: | CAPpHfdtnkqP-VJ2g8U=9QJZ5_MWQM4ZtZh_n1eq185epEoPZnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 28, 2016 at 11:02 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
wrote:
> 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?
Idea is that this kind of information is internal API and shouldn't be
exposed at SQL level. I'm not quite sure there is no tool using this
info. Do you know such tools?
> 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
Do you have any example of this information usage? If so, we can think
about providing some way of exposing it. If not, default assumption is
that this information shouldn't be exposed.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2016-03-30 09:45:18 | Re: OOM in libpq and infinite loop with getCopyStart() |
| Previous Message | Magnus Hagander | 2016-03-30 08:50:04 | Re: Missing mention of GSSAPI in MSVC's config_default.pl |