| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>, "Peter Eisentraut" <peter(at)eisentraut(dot)org> |
| Subject: | Re: pg_createsubscriber clarification |
| Date: | 2024-07-30 21:02:51 |
| Message-ID: | 1802dbe8-d136-4ea3-bc31-bffc41b2cd27@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sun, Jul 28, 2024, at 1:17 PM, Masahiko Sawada wrote:
> I think the term "synchronization phase" comes from the description in
> "29.8.1. Initial Snapshot" section[1].
Yes.
> https://www.postgresql.org/docs/17/logical-replication-architecture.html#LOGICAL-REPLICATION-SNAPSHOT
>
> How about the following?
>
> The main difference between the logical replication setup and
> pg_createsubscriber is how they synchronize table data.
> pg_createsubscriber doesn't copy the initial table data because it
> uses the tables with their initial data on the target server. It only
> does the synchronization phase, which ensures each table is brought up
> to a synchronized state by applying changes using standard logical
> replication.
I slightly modified your proposal in the attached patch.
Thoughts?
--
Euler Taveira
EDB https://www.enterprisedb.com/
| Attachment | Content-Type | Size |
|---|---|---|
| doc.patch | text/x-patch | 992 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-07-31 05:22:30 | Re: incorrect (incomplete) description for "alter domain" |
| Previous Message | David G. Johnston | 2024-07-29 17:43:24 | Re: incorrect (incomplete) description for "alter domain" |