Re: PostgreSQL shutdown modes

From: chap(at)anastigmatix(dot)net
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL shutdown modes
Date: 2022-04-02 13:39:52
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2022-04-01 13:22, Robert Haas wrote:
> I attach herewith a modest patch to rename these shutdown modes to
> more accurately correspond to their actual characteristics.

I've waited for April 2nd to submit this comment, but it seemed to me
that the
suggestion about the first-pass checkpoint in 'slow' mode is a
no-foolin' good one.
Then I wondered whether there could be an option to accompany the 'dumb'
mode that
would take a WHERE clause, to be implicitly applied to pg_stat_activity,
purpose would be to select those sessions that are ok to evict without
waiting for
them to exit. It could recognize, say, backend connections in no current
that are from your pesky app or connection pooler that holds things
open. It could
also, for example, select things in transaction state but where
current_timestamp - state_change > '5 minutes' (so it would be
re-evaluated every
so often until ready to shut down).

For conciseness (and sanity), maybe the WHERE clause could be implicitly
not to pg_stat_activity directly, but to a (virtual or actual) view that
already been restricted to client backend sessions, and already has a
for current_timestamp - state_change.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-04-02 14:43:46 Re: [PATCH] Add extra statistics to explain for Nested Loop
Previous Message Fabien COELHO 2022-04-02 13:34:51 Re: [PATCH] pgbench: add multiconnect option