From: | Pengzhou Tang <ptang(at)pivotal(dot)io> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Extend Table AM routine to get total blocks can be analyzed |
Date: | 2019-11-11 08:21:31 |
Message-ID: | CAG4reARd9z9FAca_dPGQHbHTDCd4SfQnGQCpp7TEXBGVjd7U6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Hackers,
Table AM routine already provided two custom functions to fetch sample
blocks and sample tuples,
however, the total blocks the ANALYZE can scan are still restricted to the
number of physical blocks
in a table, this doesn't work well for storages which organize blocks in
different ways than the heap.
Here is proposing to add a new method named scan_analyze_total_blocks() to
provide more flexibility,
it can return physical or logical blocks number which depends on how the
table AM implement
scan_analyze_next_block() and scan_analyze_next_tuple().
Attachment | Content-Type | Size |
---|---|---|
v1-0001-extend-tableam-scan-analyze-total-blocks.patch | application/octet-stream | 4.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2019-11-11 08:27:40 | Re: dropdb --force |
Previous Message | Amit Langote | 2019-11-11 07:59:08 | Re: adding partitioned tables to publications |