Re: Introduce MIN/MAX aggregate functions to pg_lsn

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, 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 13:57:29
Message-ID: CA+TgmoY1oy392sDxCmiS=WewtDP88=4HhKMHboFw6KDRkTuA1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-07-04 14:24:17 Re: Memory-Bounded Hash Aggregation
Previous Message Dave Cramer 2019-07-04 13:49:30 Re: Binary support for pgoutput plugin