| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: When updating ShmemVariableCache from a checkpoint record, be |
| Date: | 2010-02-17 03:10:33 |
| Message-ID: | 20100217031033.C34E97541C5@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
When updating ShmemVariableCache from a checkpoint record, be sure to set
all the values derived from oldestXid, not just that field. Brain fade in
one of my patches associated with flat file removal, exposed by a report
from Fujii Masao.
With this change, xidVacLimit should always be valid, so remove a couple of
bits of complexity associated with the previous assumption that sometimes
it wouldn't get set right away.
Modified Files:
--------------
pgsql/src/backend/access/transam:
varsup.c (r1.88 -> r1.89)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/varsup.c?r1=1.88&r2=1.89)
xlog.c (r1.373 -> r1.374)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.373&r2=1.374)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Mhasegawa | 2010-02-17 03:11:16 | pgstatsinfo - pg_statsinfo: GUC parameters in a method to send by |
| Previous Message | Tom Lane | 2010-02-17 01:48:58 | pgsql: Prevent #option dump from crashing on FORI statement with null |