From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | Zheng Li <zhengli10(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Support logical replication of DDLs |
Date: | 2022-02-24 08:56:36 |
Message-ID: | CAJ7c6TP2=_k-w0rDrqbn6A40qEQcZ=kwVf18+YsfowbFL0o3Pg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Hi Zheng,
> >Also, I suspect that implementing it may be a bit challenging. What if we
> >focus on table-level replication for now?
>
> I think it is due to the fact that the current limitations in logical
> replication are
> holding it back in major version upgrade (MVU). Online / reduced downtime MVU
> is a popular request from customers, and why we should enhance logical
> replication
> to support this use case.
>
> Also I think table-level DDL replication is actually more challenging,
> especially in
> the FOR TABLE case, due to the fact that differences are expected to
> occur between the
> source and target database. Marcos’ comment also justifies the complexity
> in this case. Whereas database-level DDL replication in the FOR ALL
> TABLE case is
> relatively simple because the source and target database are (almost) identical.
Sure, I don't insist on implementing table-level replication first.
It's up to you. My point was that it's not necessary to implement
everything at once.
--
Best regards,
Aleksander Alekseev
From | Date | Subject | |
---|---|---|---|
Next Message | Catalin Maftei | 2022-02-24 12:48:55 | alter table to multi partitions |
Previous Message | Peter J. Holzer | 2022-02-24 07:49:55 | Re: pg_upgrade from Postgresql-12 to Postgresql-13 fails with "Creating dump of database schemas postgres *failure*" |
From | Date | Subject | |
---|---|---|---|
Next Message | Aleksander Alekseev | 2022-02-24 09:02:54 | Re: PATCH: add "--config-file=" option to pg_rewind |
Previous Message | Peter Smith | 2022-02-24 08:53:33 | Re: Design of pg_stat_subscription_workers vs pgstats |