Re: logical decoding and replication of sequences
От | Tomas Vondra |
---|---|
Тема | Re: logical decoding and replication of sequences |
Дата | |
Msg-id | 7e4e23f2-193c-7bfc-7a13-d504d6ad1fe3@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: logical decoding and replication of sequences (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On 2/19/22 06:33, Amit Kapila wrote: > On Sat, Feb 19, 2022 at 7:48 AM Tomas Vondra > <tomas.vondra@enterprisedb.com> wrote: >> >> Do we need to handle both FOR ALL TABLES and FOR ALL SEQUENCES at the >> same time? That seems like a reasonable thing people might want. >> > > +1. That seems reasonable to me as well. I think the same will apply > to FOR ALL TABLES IN SCHEMA and FOR ALL SEQUENCES IN SCHEMA. > It already works for "IN SCHEMA" because that's handled as a publication object, but FOR ALL TABLES and FOR ALL SEQUENCES are defined directly in CreatePublicationStmt. Which also means you can't do ALTER PUBLICATION and change it to FOR ALL TABLES. Which is a bit annoying, but OK. It's a bit weird FOR ALL TABLES is mentioned in docs for ALTER PUBLICATION as if it was supported. regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: