Add table AM 'tid_visible'

From: Jinbao Chen <cjinbao(at)vmware(dot)com>
To: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Add table AM 'tid_visible'
Date: 2020-11-02 09:16:26
Message-ID: B9754C4A-B270-4E03-A2A4-BB0929B3FC87@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

We directly call the heap function VM_ALL_VISIBLE in the
IndexOnlyNext function. This is not in line with the design idea of
table am. If the new storage type needs to implement index only
scan, he must hack the IndexOnlyNext function.

So this patch add a new table am 'tid_visible' to test visibility
of tid. So that index only scan can completely use table AM.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2020-11-02 09:28:15 Re: Collation versioning
Previous Message Heikki Linnakangas 2020-11-02 09:03:29 Split copy.c