| From: | heikki(at)postgresql(dot)org (Heikki Linnakangas) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Remove piece of code to zero out minRecoveryPoint when starting |
| Date: | 2010-02-08 09:08:52 |
| Message-ID: | 20100208090852.353BE7541B9@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Remove piece of code to zero out minRecoveryPoint when starting crash
recovery. It's zeroed out whenever a checkpoint is written, so the only
scenario where the removed code did anything is when you kill archive
recovery, remove recovery.conf, and start up the server, so that it goes
into crash recovery instead. That's a "don't do that" scenario, but it
seems better to not clear minRecoveryPoint but instead update it like we
do in archive recovery, which is what will now happen.
Modified Files:
--------------
pgsql/src/backend/access/transam:
xlog.c (r1.368 -> r1.369)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.368&r2=1.369)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-02-08 13:41:06 | pgsql: Update high availability/replication documentation chart for new |
| Previous Message | Tom Lane | 2010-02-08 05:53:55 | pgsql: Remove CatalogCacheFlushRelation, and the reloidattr |