is cachedFetchXid ever invalidated?

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: is cachedFetchXid ever invalidated?
Date: 2010-12-02 01:48:36
Message-ID: 1291254516.23262.65.camel@jdavis-ux.asterdata.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I can't see any place that "cachedFetchXid" is ever invalidated.
Shouldn't it be invalidated before transaction ID wraparound?

It's difficult to construct a test case to show whether this is a
problem or not, but I couldn't find how this is solved in the code. My
understanding is that, before truncating the clog, we need to make sure
that there are no references to any transaction IDs that would be cut
off.

Regards,
Jeff Davis

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ghatpande 2010-12-02 02:11:18 Re: Proposal: First step towards Intelligent, integrateddatabase
Previous Message Craig Ringer 2010-12-02 01:02:16 Re: [HACKERS] Improved JDBC driver part 2