Message-ID: <79d2a8c1-8fa9-4104-a1dd-529a8ad9b7a7@gmx.net>
Date: Thu, 1 Aug 2024 11:05:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Logical replication slots on slaves/replicas?
To: pgsql-general@lists.postgresql.org
References: <AB145716-132B-4BB5-AC69-32EA9FDE4633@attendium.com>
Content-Language: de-DE
From: shammat@gmx.net
In-Reply-To: <AB145716-132B-4BB5-AC69-32EA9FDE4633@attendium.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:Mq1L4Dzwg5s=;WoVIFuJHISM+CcItMAk9Iey3xs6
 QoXUrbqXRluDdBF3qJ0EiddSrS/znhmDCcLIiYVEtF9wWiAx6CjXtwMdR2wumb9hQdiec1aGd
 KkVVidaALIg13q526baerEDpkgt9/0B4512WcdHPahtvpxD9ac604NUR5Q0x5IZCGGy0skryE
 eI+irJdhlWwzvHNfdhhmR1Q+n/xNneUyQo08AVGgrFq4i9/LN8MzWt55U8MQt0IHT9Medff77
 n9K8Y1miZF55bNvFHjtnE1i8Tpkhm9UkBZOE5x5E5sjTP/hRyan9cbKBcqBYgX0MUvejbrBux
 WeYvjribiwHrAKyRjOraVIl2xRHsGPY5mR2LSp1QHPznHb7y3ZJQs5OoBbbVeOTUMupu9AQdC
 94MtLDNKmHmtyXzPo55HNXngjqTMvgp8DEVsZjIpeg/YAy17fB9PBeGxxOtH8JzwrlsLlBA3Z
 JmF4ftv4fzLIkq8rYt8Xv3giwXTCZz1L/etMOEpgj0UCXVj6789D+gGhzlsbZVayQDRcBsXLy
 XQRWI3Cqz/wasfTDB98LmWZYG9rtVX4252/OlbXpMyYlZvRsLoS/iuuwiXNTdGo7u2HDJFwjI
 q5pdSEcRYfb6toRGW0P4Iu2CF2CRjNnZ9MXIIzQVVBvZ0saEGVgGp2AVj97T59r7qddmtC6oY
 pXNu64XbePIdtd0JHD7gPWonki7xt99ctiu0wNVQd664aVIbOmyFmPyV1irKdIeT40RfMSbKY
 lGgvw3wBDLxE6WpbzCmnbFqkWrJoPSp1hMx0nWMM1GoMmn0o+RTAH8+yf9Wx5ryT2lhVb5SGz
 K/Hk1uy73ZLZExko3UlfF+3A==
Archived-At: <https://www.postgresql.org/message-id/79d2a8c1-8fa9-4104-a1dd-529a8ad9b7a7%40gmx.net>
Precedence: bulk

Piotr Andreassen Blasiak schrieb am 01.08.2024 um 10:42:
> I know that currently logical replication slots are available only
> for primary servers. Is there any plan to add this feature to read
> slaves as well? My problem is this:
>
> I want to use debezium to stream changes from postgresql. But, if I
> stream changes from the master I can not query my read slaves for
> related data to these changes - I need to always query the master
> which is not scalable. So either I need a way to be able to know
> when the change has been propagated to my read replica so that I can
> reliably query it, or I am hoping I can simply read all the changes
> from the read replica which will mean it is already up to date when
> I query it.

I don't really know how Debezium uses this, but will this enhancement
in Postgres 17 help here?

https://www.postgresql.org/docs/17/functions-admin.html#PG-SYNC-REPLICATIO=
N-SLOTS

> Synchronize the logical failover replication slots from the primary
> server to the standby server. This function can only be executed on
> the standby server. Temporary synced slots, if any, cannot be used
> for logical decoding and must be dropped after promotion.