expose confirmed_flush for replication slots

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: expose confirmed_flush for replication slots
Date: 2015-07-08 11:57:26
Message-ID: 559D1026.5080303@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


I had some trouble today with a misbehaving logical replication client
which had confirmed a flush of an LSN far into the future. Debugging it
was a bit of a pain for a number of reasons, but I think the most
important one was that confirmed_flush isn't exposed in
pg_stat_replication_slots. Attached patch exposes it, as
confirmed_flush_lsn (to make it look like restart_lsn; not sure whether
we should just keep the internal name or not).

Adding this one to the next commit fest, but any feedback welcome in the


Attachment Content-Type Size
confirmed_flush.patch text/plain 3.9 KB


Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2015-07-08 12:01:15 Re: expose confirmed_flush for replication slots
Previous Message Cédric Villemain 2015-07-08 10:02:39 Re: pg_receivexlog --create-slot-if-not-exists