| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | "Shlok Kyal" <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, "Andrew Atkinson" <andyatkinson(at)gmail(dot)com>, "Peter Smith" <smithpb2250(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add publisher and subscriber to glossary documentation. |
| Date: | 2024-03-15 04:37:31 |
| Message-ID: | dbdd5a52-948a-40b5-848f-e9e414cbdbf1@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 15, 2024, at 1:14 AM, Amit Kapila wrote:
> I think node should mean instance for both physical and logical
> replication, otherwise, it would be confusing. We need both the usages
> as a particular publication/subscription is defined at the database
> level but the server on which we define those is referred to as a
> node/instance.
If you are creating a subscription that connects to the same instance
(replication between 2 databases in the same cluster), your definition is not
correct and Alvaro's definition is accurate. The node definition is closely
linked to the connection string. While the physical replication does not
specify a database (meaning "any database" referring to an instance), the
logical replication requires a database.
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2024-03-15 04:44:49 | Re: Introduce XID age and inactive timeout based replication slot invalidation |
| Previous Message | Ajin Cherian | 2024-03-15 04:20:51 | Re: Skip collecting decoded changes of already-aborted transactions |