pgsql: Update the location of last removed WAL segment in shared memory - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: Update the location of last removed WAL segment in shared memory
Date
Msg-id 20100412104043.1B42D7541D0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Update the location of last removed WAL segment in shared memory only
after actually removing one, so that if we can't remove segments because
WAL archiving is lagging behind, we don't unnecessarily forbid streaming
the old not-yet-archived segments that are still perfectly valid. Per
suggestion from Fujii Masao.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.392 -> r1.393)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.392&r2=1.393)
    pgsql/src/include/access:
        xlog_internal.h (r1.31 -> r1.32)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/xlog_internal.h?r1=1.31&r2=1.32)

pgsql-committers by date:

Previous
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Need to use the start pointer of a block we read from WAL segment
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Spell out full archive directory specification in 'test -f'