From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: old_snapshot_threshold's interaction with hash index |
Date: | 2016-05-01 06:43:02 |
Message-ID: | CAA4eK1Jm=PXXwk_vrtV05+Mb32s08VJOBLrjj6FQdROHqFW8Og@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 1, 2016 at 12:05 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Yury Zhuravlev | 2016-05-01 09:24:55 | Re: Windows 7, Visual Studio 2010: building PgAdmin3 |
Previous Message | Amit Kapila | 2016-05-01 06:35:16 | old_snapshot_threshold's interaction with hash index |