Re: old_snapshot_threshold's interaction with hash index - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: old_snapshot_threshold's interaction with hash index
Date
Msg-id CAA4eK1Jm=PXXwk_vrtV05+Mb32s08VJOBLrjj6FQdROHqFW8Og@mail.gmail.com
Whole thread Raw
In response to old_snapshot_threshold's interaction with hash index  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: old_snapshot_threshold's interaction with hash index  (Kevin Grittner <kgrittn@gmail.com>)
List pgsql-hackers
On Sun, May 1, 2016 at 12:05 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
Currently we do the test for old snapshot (TestForOldSnapshot) for hash indexes while scanning them.  Does this test makes any sense for hash indexes considering LSN on hash index will always be zero (as hash indexes are not WAL-logged)?  It seems to me that PageLSN check in TestForOldSnapshot() will always return false which means that the error "snapshot too old" won't be generated for hash indexes.

Am I missing something here, if not, then I think we need a way to prohibit pruning for hash indexes based on old_snapshot_threshold?  


What I mean to say here is prohibit pruning the relation which has hash index based on old_snapshot_threshold. 



With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: old_snapshot_threshold's interaction with hash index
Next
From: Yury Zhuravlev
Date:
Subject: Re: Windows 7, Visual Studio 2010: building PgAdmin3