Re: SQL access to access method details

Поиск
Список
Период
Сортировка
От Alexander Korotkov
Тема Re: SQL access to access method details
Дата
Msg-id CAPpHfdtnkqP-VJ2g8U=9QJZ5_MWQM4ZtZh_n1eq185epEoPZnw@mail.gmail.com
обсуждение исходный текст
Ответ на SQL access to access method details  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Дерево обсуждения
On Mon, Mar 28, 2016 at 11:02 PM, Jim Nasby <Jim.Nasby@bluetreble.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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Missing mention of GSSAPI in MSVC's config_default.pl
Следующее
От: Aleksander Alekseev
Дата:
Сообщение: Re: OOM in libpq and infinite loop with getCopyStart()