Re: Asynchronous and "direct" IO support for PostgreSQL.

From: Alexey Lesovsky <alexey(dot)lesovsky(at)dataegret(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Asynchronous and "direct" IO support for PostgreSQL.
Date: 2021-02-25 17:07:22
Message-ID: d97b536e-4017-5e27-6ca6-e2f4f66802f8@dataegret.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 25.02.2021 02:03, Andres Freund wrote:
>> pg_stat_aio_backends.
>> This stat is based on COUNTERs, which is great, but the issue here is that
>> its lifespan is limited by the lifespan of the backend processes - once the
>> backend exits the stat will no longer be available - which could be
>> inappropriate in workloads with short-lived backends.
> There's a todo somewhere to roll over the per-connection stats into a
> global stats piece on disconnect. In addition I was thinking of adding a
> view that sums up the value of "already disconnected backends" and the
> currently connected ones. Would that mostly address your concerns?

Yes, approach with separated stats for live and disconnected backends
looks good and solves problem with "stats loss".

Or it can be done like a stats for shared objects in pg_stat_databases,
where there is a special NULL database is used.

Regards, Alexey

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2021-02-25 17:48:51 Re: libpq debug log
Previous Message John Naylor 2021-02-25 16:33:23 Re: Removing support for COPY FROM STDIN in protocol version 2