pgsql: Update the location of last removed WAL segment in shared memory

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Update the location of last removed WAL segment in shared memory
Date: 2010-04-12 10:40:43
Message-ID: 20100412104043.1B42D7541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2010-04-12 19:08:28 pgsql: Spell out full archive directory specification in 'test -f'
Previous Message Heikki Linnakangas 2010-04-12 10:18:50 pgsql: Need to use the start pointer of a block we read from WAL segment