News for hackers. Stuff that matters.

A comment on Postgres, Kafka, and a mysterious 100 GB. Parent comment

Re:Postgres, Kafka, and a mysterious 100 GB by Izkata on Tuesday December 07, 2021 @08:45PM (#29480421)
> Logical replication slots should have timeouts where if you haven't read the WAL record in say 24 hours it should be dropped. Make it configurable and set a sane default, problem solved.

In other words, replication without using replication slots. Postgres has had it for a long time, although the limit is set in disk usage rather than time.

(unless specifically logical replication and/or debezium don't support this?)

[ Parent | on HN ]
Re:Postgres, Kafka, and a mysterious 100 GB by voganmother42 on Tuesday December 07, 2021 @09:58PM (#29480807)
Postgres replication slots support a max size (since 13) specifically to deal with this scenario (prior to that needed to setup monitoring/intervention outside the db)
[ Parent | on HN ]