| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | hlinnakangas(at)vmware(dot)com |
| Cc: | ants(at)cybertec(dot)at, simon(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 9.2.3 crashes during archive recovery |
| Date: | 2013-02-26 06:52:04 |
| Message-ID: | 20130226.155204.115316458.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
However this has become useless, I want to explain about how this
works.
> > I tried to postpone smgrtruncate TO the next checktpoint.
>
> Umm, why? I don't understand this patch at all.
This inhibits truncate files after (quite vague in the patch:-)
the previous checkpoint by hindering the deleted tuples from
vacuum then hindering the vm pages from truncation. They are
truncated only If no tuples is deleted on the pages correspond to
them since the last checkpoint. Finally any nonexistent pages in
visibility maps won't be touched after the consistency point -
which is after the last checkpoint - on archive recovery.
# Umm.. sorry for confused explanation...
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-02-26 07:06:24 | Re: [PATCH] Add PQconninfoParseParams and PQconninfodefaultsMerge to libpq |
| Previous Message | Kyotaro HORIGUCHI | 2013-02-26 06:25:48 | Re: 9.2.3 crashes during archive recovery |