Re: Should rename "startup process" to something else?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should rename "startup process" to something else?
Date: 2021-11-18 14:17:50
Message-ID: CA+TgmobY1ByNq=2-SAtoqv0axusF3NEDs7z31P8SbgMOYnfzPg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 18, 2021 at 5:34 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> The startup process main function looks to be to do some
> initialization required for recovery and do the recovery, exit if it
> is a crash recovery or stay there if it is a standby recovery. Apart
> from these I'm not sure it does any non-recovery tasks. Does the
> startup process have any relevance or work to do if the server state
> is DB_SHUTDOWNED i.e the server was shutdown properly? I think yes,
> although it doesn't enter the recovery/REDO loop, it does a bunch of
> other things like updating the control file, pre-allocating WAL files,
> updating shared memory state to allow other backends to write WAL and
> so on.

That's true, but those tasks are very brief. Nobody's going to get too
confused by a "recovery" process that shows up for a few milliseconds
when there's no recovery to be done. Having a "startup" process that
sticks around forever on a standy, though, actually is confusing.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeevan Ladhe 2021-11-18 14:24:37 Re: Teach pg_receivewal to use lz4 compression
Previous Message Alexander Kuzmenkov 2021-11-18 14:11:16 [RFC] ASOF Join