public inbox for [email protected]
help / color / mirror / Atom feedlogical replication, with a replication slot but still getting "requested WAL segment has already been removed"
2+ messages / 2 participants
[nested] [flat]
* logical replication, with a replication slot but still getting "requested WAL segment has already been removed"
@ 2025-12-22 21:14 Sbob <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Sbob @ 2025-12-22 21:14 UTC (permalink / raw)
To: [email protected]
All;
We have setup logical replication for some very large tables, both
publisher and subscriber are running postgresql v14, however even though
the locical replication is using a replication slot we keep getting this
error:
2025-12-21 23:25:50.452 UTC [2131314] LOG: logical replication apply
worker for subscription "bigtables_sub" has started
2025-12-21 23:25:50.987 UTC [2131314] ERROR: could not receive data
from WAL stream: ERROR: requested WAL segment 000000020000089F00000098
has already been removed
Thanks for any help
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: logical replication, with a replication slot but still getting "requested WAL segment has already been removed"
@ 2025-12-23 10:17 Laurenz Albe <[email protected]>
parent: Sbob <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Laurenz Albe @ 2025-12-23 10:17 UTC (permalink / raw)
To: Sbob <[email protected]>; [email protected]
On Mon, 2025-12-22 at 14:14 -0700, Sbob wrote:
> We have setup logical replication for some very large tables, both publisher and subscriber
> are running postgresql v14, however even though the locical replication is using a replication
> slot we keep getting this error:
>
> 2025-12-21 23:25:50.452 UTC [2131314] LOG: logical replication apply worker for subscription "bigtables_sub" has started
> 2025-12-21 23:25:50.987 UTC [2131314] ERROR: could not receive data from WAL stream: ERROR: requested WAL segment 000000020000089F00000098 has already been removed
Look into "pg_replication_slots" on the publisher, perhaps the "wal_status" has changed
to "unreserved" or "lost". One possible cause for that could be the setting of
"max_slot_wal_keep_size" on the publisher.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-12-23 10:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-12-22 21:14 logical replication, with a replication slot but still getting "requested WAL segment has already been removed" Sbob <[email protected]>
2025-12-23 10:17 ` Laurenz Albe <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox