<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Replication Slots on Postgres Scripts</title><link>https://www.postgresscripts.com/tags/replication-slots/</link><description>Recent content in Replication Slots on Postgres Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>PostgresScripts.com</copyright><lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.postgresscripts.com/tags/replication-slots/index.xml" rel="self" type="application/rss+xml"/><item><title>Monitor Logical Replication Slot Stats with pg_stat_replication_slots</title><link>https://www.postgresscripts.com/post/monitor-logical-replication-slot-stats-with-pg-stat-replication-slots/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.postgresscripts.com/post/monitor-logical-replication-slot-stats-with-pg-stat-replication-slots/</guid><description>
&lt;h2 id="monitor-logical-replication-slot-stats-with-pg_stat_replication_slots"&gt;Monitor Logical Replication Slot Stats with pg_stat_replication_slots&lt;/h2&gt;
&lt;p&gt;How full does a logical decoding worker's memory buffer get before PostgreSQL gives up holding a transaction in RAM and starts writing it to disk? &lt;a href="https://www.postgresql.org/docs/current/monitoring-stats.html"&gt;pg_stat_replication_slots&lt;/a&gt; answers that question per slot, in concrete numbers — spilled-transaction counts, spilled bytes, and the streamed alternative — without grepping WAL sender logs for a spill message that may never get written. It's a narrow view with a narrow job: reporting on the internal memory accounting of logical decoding, not the replay lag a standby is carrying.&lt;/p&gt;</description></item></channel></rss>