| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dan shmidt <dshmidt(at)hotmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical Replication of Multiple Schema Versions |
| Date: | 2019-12-11 16:13:51 |
| Message-ID: | c131c6f5-35db-cbde-f35b-3532a7181fe5@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2019-12-10 08:55, Dan shmidt wrote:
> What is the correct way to perform such an operation?
> Is there a way to keep constraint #1 or the only option is to not allow
> "breaking" schema changes between versions.
It all depends on the specific schema changes you want to make. You can
add columns on the subscriber and remove columns on the publisher
without breaking things (unless there are not-null constraints).
Renaming columns will break replication until you rename them
everywhere. Column type changes will usually just work as long as the
data fits into both the old and the new type.
You really need to carefully plan and test each class of scenarios
separately.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-12-11 16:31:00 | Re: PGUSER and initdb |
| Previous Message | Stephen Frost | 2019-12-11 15:52:47 | Re: AW: AW: secure deletion of archived logs |