Re: strange nbtree corruption report - Mailing list pgsql-hackers

From Tom Lane
Subject Re: strange nbtree corruption report
Date
Msg-id 1189.1321933403@sss.pgh.pa.us
Whole thread Raw
In response to Re: strange nbtree corruption report  (Noah Misch <noah@leadboat.com>)
Responses Re: strange nbtree corruption report
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> Just a suspicion ... when looking at the B-tree page reclamation algorithm, I
> had a thought that the logic in _bt_page_recyclable() was obsolete as of the
> introduction (in 8.3) of xid-free read-only transactions.  A transaction
> without a persistent xid does not hold back RecentXmin, so how could waiting
> for a RecentXmin window to pass prove that no scan still holds a link to the
> page?  Similarly, running VACUUMs do not hold back RecentXmin.

Uh, sure they do.  It's their advertised snapshot xmin that counts, not
their own xid (if any).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rename a database that has connections
Next
From: Mark Kirkwood
Date:
Subject: Re: Rename a database that has connections