Re: Oddity with psql \d and pg_table_is_visible

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Oddity with psql \d and pg_table_is_visible
Дата
Msg-id 21451.1189020470@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Oddity with psql \d and pg_table_is_visible  (Decibel! <decibel@decibel.org>)
Ответы Re: Oddity with psql \d and pg_table_is_visible  (Decibel! <decibel@decibel.org>)
Список pgsql-hackers
Decibel! <decibel@decibel.org> writes:
> While this is correct on a per-relation level, I'm thinking that it's
> not what we'd really like to have happen in psql. What I'd like \d to do
> is show me everything in any schema that's in my search_path, even if
> there's something higher in the search_path that would over-ride it.
> ISTM that's what most people would expect out of \d.

I don't agree with that reasoning in the least, particularly not if you
intend to "fix" it by redefining pg_table_is_visible() ...

What will happen if we change \d to work that way is that it will show
you a table, and you'll try to access it, and you'll get the wrong table
because the access will go to the one that really is visible.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Should pointers to PGPROC be volatile-qualified?
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: Reducing Transaction Start/End Contention