Re: BUG #15263: pg_dump / psql failure. When loading, psql does notsee function-based constraints or indices

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #15263: pg_dump / psql failure. When loading, psql does notsee function-based constraints or indices
Дата
Msg-id CAKFQuwa+X47iUN2A-cjLOdB1OR-jxyPvP=a7KoFJNcnLZ1ppKw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #15263: pg_dump / psql failure. When loading, psql does notsee function-based constraints or indices  (firstname lastname <ceccareb@talusmusic.com>)
Список pgsql-bugs
Дерево обсуждения
On Wed, Jul 18, 2018 at 2:47 PM, firstname lastname <ceccareb@talusmusic.com> wrote:
In the end, a person should be able to copy his objects a different schema; therefore, one would not want to hard-code a schema name to every object.

​This is basically the issue.  By allowing schema to be flexible you expose your system to masquerading.  A more secure, yet still reasonable, posture is to treat the namespace layout of the database as a fundamental property of the model.  Where that starts to break down is dealing with multi-tenant situations and trying to have shared and not-shared schema components. Not sure what the good solutions are if your application wants to operate under that model - but that affects a minority of people and doesn't seem to be the case here.

David J.

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #15263: pg_dump / psql failure. When loading, psql does notsee function-based constraints or indices
Следующее
От: Amit Langote
Дата:
Сообщение: Re: BUG #15283: Query Result equal 0 for partitioned table