| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Surafel Temesgen <surafel3000(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Introduce MIN/MAX aggregate functions to pg_lsn |
| Date: | 2019-07-04 16:48:06 |
| Message-ID: | CAFcNs+qjvHfRAXZ3=91wz2swLGQhF9g6bujHY4aA148V8c98uw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 4, 2019 at 5:17 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jul 02, 2019 at 11:31:49AM -0300, Fabrízio de Royes Mello wrote:
> > New version attached.
>
> This looks in pretty good shape to me, and no objections from me to
> get those functions as the min() flavor is useful for monitoring WAL
> retention for complex deployments.
>
> Do you have a particular use-case in mind for max() one? I can think
> of at least one case: monitoring the flush LSNs of a set of standbys
> to find out how much has been replayed at most.
>
I use min/max to measure the amount of generated WAL (diff) during some
periods based on wal position stored in some monitoring system.
Regards,
--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2019-07-04 16:48:24 | Re: Introduce MIN/MAX aggregate functions to pg_lsn |
| Previous Message | Tomas Vondra | 2019-07-04 16:47:31 | Re: duplicate key entries for primary key -- need urgent help |