| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: pg_stat_wal_receiver and flushedUpto/writtenUpto |
| Date: | 2020-05-15 23:05:39 |
| Message-ID: | 20200515230539.GC212736@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| wal-receiver-stat-v2.patch | text/x-diff | 7.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-05-15 23:24:28 | Re: pg13: xlogreader API adjust |
| Previous Message | Ranier Vilela | 2020-05-15 22:33:45 | Re: calling procedures is slow and consumes extra much memory against calling function |