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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
