| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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:24 |
| Message-ID: | CAFcNs+pvhjtU5HXscQ0YnJRXYxUZ62qK-k9WNU7BnsTmLneG7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 4, 2019 at 10:57 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Jul 4, 2019 at 4:17 AM Michael Paquier <michael(at)paquier(dot)xyz>
wrote:
> > 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.
>
> It would be pretty silly to have one and not the other, regardless of
> whether we can think of an immediate use case.
>
+1
--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kumar, Pawan (Nokia - IN/Bangalore) | 2019-07-04 17:34:21 | RE: duplicate key entries for primary key -- need urgent help |
| Previous Message | Fabrízio de Royes Mello | 2019-07-04 16:48:06 | Re: Introduce MIN/MAX aggregate functions to pg_lsn |