Skip site navigation (1) Skip section navigation (2)

pgsql: Move the responsibility for calling StartupXLOG into

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Move the responsibility for calling StartupXLOG into
Date: 2010-04-20 01:38:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Move the responsibility for calling StartupXLOG into InitPostgres, for
those process types that go through InitPostgres; in particular, bootstrap
and standalone-backend cases.  This ensures that we have set up a PGPROC
and done some other basic initialization steps (corresponding to the
if (IsUnderPostmaster) block in AuxiliaryProcessMain) before we attempt to
run WAL recovery in a standalone backend.  As was discovered last September,
this is necessary for some corner-case code paths during WAL recovery,
particularly end-of-WAL cleanup.

Moving the bootstrap case here too is not necessary for correctness, but it
seems like a good idea since it reduces the number of distinct code paths.

Modified Files:
        bootstrap.c (r1.260 -> r1.261)
        postgres.c (r1.592 -> r1.593)
        postinit.c (r1.208 -> r1.209)

pgsql-committers by date

Next:From: Robert HaasDate: 2010-04-20 11:15:07
Subject: pgsql: Rename standby_keep_segments to wal_keep_segments.
Previous:From: Robert HaasDate: 2010-04-20 00:29:35
Subject: Re: pgsql: Update docs as to when WAL logging can be skipped.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group