Re: pg_stat_wal_receiver and flushedUpto/writtenUpto - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_stat_wal_receiver and flushedUpto/writtenUpto
Date
Msg-id 20200515230539.GC212736@paquier.xyz
Whole thread Raw
In response to Re: pg_stat_wal_receiver and flushedUpto/writtenUpto  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: pg_stat_wal_receiver and flushedUpto/writtenUpto
List pgsql-hackers
On Fri, May 15, 2020 at 01:43:11PM -0400, Alvaro Herrera wrote:
> Why do you put the column at the end?  I would put written_lsn before
> flushed_lsn.

Fine by me.  I was thinking yesterday about putting the written
position after the flushed one, and finished with something that maps
with the structure.

> Since this requires a catversion bump, I think it'd be best to do it
> before beta1 next week.

Yes.  What do you think of the attached?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: calling procedures is slow and consumes extra much memory againstcalling function
Next
From: Alvaro Herrera
Date:
Subject: Re: pg13: xlogreader API adjust