Re: PostgreSQL 16 release announcement draft
Jonathan S. Katz <jkatz@postgresql.org>
From: "Jonathan S. Katz" <jkatz@postgresql.org>
To: Erik Rijkers <er@xs4all.nl>, David Rowley <dgrowleyml@gmail.com>
Cc: jian he <jian.universality@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
chelseadole@gmail.com
Date: 2023-08-26T02:51:43Z
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@postgresql.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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Support "Right Anti Join" plan shapes.
- 16dc2703c541 16.0 cited
-
Improve performance of ORDER BY / DISTINCT aggregates
- 1349d2790bf4 16.0 cited