From: | Kartyshov Ivan <i(dot)kartyshov(at)postgrespro(dot)ru> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | proposal: get oldest LSN - function |
Date: | 2016-02-26 15:45:14 |
Message-ID: | 56D0730A.2060508@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello, I want to suggest a client-side little function, implemented
in the attached patch.
Function pg_oldest_xlog_location gets us the oldest LSN (Log Sequence
Number) in xlog.
It is useful additional tool for DBA (we can get replicationSlotMinLSN,
so why not in master), it can show us, if xlog replication or wal-sender
is working properly or indicate if replication on startup can get up to
date with master, or after long turnoff must be recovered from archive.
Anyway, does it look useful enough to be part of postgres?
I guess I should push this to commitfest if that's the case.
Best regards,
--
Ivan Kartyshov
Postgres Professional: www.postgrespro.com
Russian Postgres Company
Attachment | Content-Type | Size |
---|---|---|
oldestLSN.patch | text/x-patch | 5.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Roma Sokolov | 2016-02-26 15:46:13 | [PATCH] fix DROP OPERATOR to reset links to itself on commutator and negator |
Previous Message | Ivan Kartyshov | 2016-02-26 15:34:27 | Re: Sanity checking for ./configure options? |