| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Erik Rijkers <er(at)xs4all(dot)nl>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, chelseadole(at)gmail(dot)com |
| Subject: | Re: PostgreSQL 16 release announcement draft |
| Date: | 2023-08-26 02:51:43 |
| Message-ID: | 81c32662-4388-eb05-6dbd-9dc8474f9629@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/24/23 11:17 AM, Erik Rijkers wrote:
> Op 8/24/23 om 16:32 schreef Jonathan S. Katz:
>> On 8/23/23 5:07 PM, David Rowley wrote:
>>> On Thu, 24 Aug 2023 at 05:55, Jonathan S. Katz <jkatz(at)postgresql(dot)org>
>>> wrote:
>
> Hi,
>
> When v15 docs have:
>
> "27.2.7. Cascading Replication
> The cascading replication feature allows a standby server to accept
> replication connections and stream WAL records to other standbys, acting
> as a relay. This can be used to reduce the number of direct connections
> to the primary and also to minimize inter-site bandwidth overheads."
>
> why then, in the release draft, is that capability mentioned as
> something that is new for v16?
> "
> In PostgreSQL 16, users can perform logical decoding from a standby
> instance, meaning a standby can publish logical changes to other servers.
> "
>
> Is there a difference between the two?
Yes. Those docs refer to **physical** replication, where a standby can
continue to replicate WAL records to other standbys. In v16, standbys
can now publish changes over **logical** replication.
Thanks,
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hongxu Ma | 2023-08-26 03:29:44 | PSQL error: total cell count of XXX exceeded |
| Previous Message | Jonathan S. Katz | 2023-08-26 02:50:24 | Re: PostgreSQL 16 release announcement draft |