Re: why can't a table be part of the same publication as its schema

Поиск
Список
Период
Сортировка
От Mark Dilger
Тема Re: why can't a table be part of the same publication as its schema
Дата
Msg-id 596EA671-66DF-4285-8560-0270DC062353@enterprisedb.com
обсуждение исходный текст
Ответ на Re: why can't a table be part of the same publication as its schema  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: why can't a table be part of the same publication as its schema  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers

> On Sep 9, 2022, at 8:18 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> Things might be clearer if we'd made the syntax "ALTER PUBLICATION p1
> { ADD | DROP } { TABLE | SCHEMA } name". I don't understand why we
> used this ALL TABLES IN SCHEMA language.

The conversation, as I recall, was that "ADD SCHEMA foo" would only mean all tables in foo, until publication of other
objecttypes became supported, at which point "ADD SCHEMA foo" would suddenly mean more than it did before.  People
mightfind that surprising, so the "ALL TABLES IN" was intended to future-proof against surprising behavioral changes. 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






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

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: Making autovacuum logs indicate if insert-based threshold was the triggering condition
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Making autovacuum logs indicate if insert-based threshold was the triggering condition