2011-08-25 06:06:16 +02:00
|
|
|
CREATE EXTENSION pgstattuple;
|
|
|
|
|
--
|
|
|
|
|
-- It's difficult to come up with platform-independent test cases for
|
|
|
|
|
-- the pgstattuple functions, but the results for empty tables and
|
|
|
|
|
-- indexes should be that.
|
|
|
|
|
--
|
2012-12-05 08:58:03 +01:00
|
|
|
create table test (a int primary key, b int[]);
|
2013-07-18 20:50:20 +02:00
|
|
|
select * from pgstattuple('test');
|
|
|
|
|
table_len | tuple_count | tuple_len | tuple_percent | dead_tuple_count | dead_tuple_len | dead_tuple_percent | free_space | free_percent
|
|
|
|
|
-----------+-------------+-----------+---------------+------------------+----------------+--------------------+------------+--------------
|
|
|
|
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
|
|
|
|
|
(1 row)
|
|
|
|
|
|
2011-08-25 06:06:16 +02:00
|
|
|
select * from pgstattuple('test'::text);
|
|
|
|
|
table_len | tuple_count | tuple_len | tuple_percent | dead_tuple_count | dead_tuple_len | dead_tuple_percent | free_space | free_percent
|
|
|
|
|
-----------+-------------+-----------+---------------+------------------+----------------+--------------------+------------+--------------
|
|
|
|
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
|
|
|
|
|
(1 row)
|
|
|
|
|
|
2013-07-18 20:50:20 +02:00
|
|
|
select * from pgstattuple('test'::name);
|
|
|
|
|
table_len | tuple_count | tuple_len | tuple_percent | dead_tuple_count | dead_tuple_len | dead_tuple_percent | free_space | free_percent
|
|
|
|
|
-----------+-------------+-----------+---------------+------------------+----------------+--------------------+------------+--------------
|
|
|
|
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
|
|
|
|
|
(1 row)
|
|
|
|
|
|
2011-08-25 06:06:16 +02:00
|
|
|
select * from pgstattuple('test'::regclass);
|
|
|
|
|
table_len | tuple_count | tuple_len | tuple_percent | dead_tuple_count | dead_tuple_len | dead_tuple_percent | free_space | free_percent
|
|
|
|
|
-----------+-------------+-----------+---------------+------------------+----------------+--------------------+------------+--------------
|
|
|
|
|
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
|
|
|
|
|
(1 row)
|
|
|
|
|
|
2013-07-18 20:50:20 +02:00
|
|
|
select pgstattuple(oid) from pg_class where relname = 'test';
|
|
|
|
|
pgstattuple
|
|
|
|
|
---------------------
|
|
|
|
|
(0,0,0,0,0,0,0,0,0)
|
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
|
|
select pgstattuple(relname) from pg_class where relname = 'test';
|
|
|
|
|
pgstattuple
|
|
|
|
|
---------------------
|
|
|
|
|
(0,0,0,0,0,0,0,0,0)
|
|
|
|
|
(1 row)
|
|
|
|
|
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
select version, tree_level,
|
|
|
|
|
index_size / current_setting('block_size')::int as index_size,
|
|
|
|
|
root_block_no, internal_pages, leaf_pages, empty_pages, deleted_pages,
|
|
|
|
|
avg_leaf_density, leaf_fragmentation
|
|
|
|
|
from pgstatindex('test_pkey');
|
2011-08-25 06:06:16 +02:00
|
|
|
version | tree_level | index_size | root_block_no | internal_pages | leaf_pages | empty_pages | deleted_pages | avg_leaf_density | leaf_fragmentation
|
|
|
|
|
---------+------------+------------+---------------+----------------+------------+-------------+---------------+------------------+--------------------
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | NaN | NaN
|
2011-08-25 06:06:16 +02:00
|
|
|
(1 row)
|
|
|
|
|
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
select version, tree_level,
|
|
|
|
|
index_size / current_setting('block_size')::int as index_size,
|
|
|
|
|
root_block_no, internal_pages, leaf_pages, empty_pages, deleted_pages,
|
|
|
|
|
avg_leaf_density, leaf_fragmentation
|
|
|
|
|
from pgstatindex('test_pkey'::text);
|
2013-07-18 20:50:20 +02:00
|
|
|
version | tree_level | index_size | root_block_no | internal_pages | leaf_pages | empty_pages | deleted_pages | avg_leaf_density | leaf_fragmentation
|
|
|
|
|
---------+------------+------------+---------------+----------------+------------+-------------+---------------+------------------+--------------------
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | NaN | NaN
|
2013-07-18 20:50:20 +02:00
|
|
|
(1 row)
|
|
|
|
|
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
select version, tree_level,
|
|
|
|
|
index_size / current_setting('block_size')::int as index_size,
|
|
|
|
|
root_block_no, internal_pages, leaf_pages, empty_pages, deleted_pages,
|
|
|
|
|
avg_leaf_density, leaf_fragmentation
|
|
|
|
|
from pgstatindex('test_pkey'::name);
|
2013-07-18 20:50:20 +02:00
|
|
|
version | tree_level | index_size | root_block_no | internal_pages | leaf_pages | empty_pages | deleted_pages | avg_leaf_density | leaf_fragmentation
|
|
|
|
|
---------+------------+------------+---------------+----------------+------------+-------------+---------------+------------------+--------------------
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | NaN | NaN
|
2013-07-18 20:50:20 +02:00
|
|
|
(1 row)
|
|
|
|
|
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
select version, tree_level,
|
|
|
|
|
index_size / current_setting('block_size')::int as index_size,
|
|
|
|
|
root_block_no, internal_pages, leaf_pages, empty_pages, deleted_pages,
|
|
|
|
|
avg_leaf_density, leaf_fragmentation
|
|
|
|
|
from pgstatindex('test_pkey'::regclass);
|
2013-07-18 20:50:20 +02:00
|
|
|
version | tree_level | index_size | root_block_no | internal_pages | leaf_pages | empty_pages | deleted_pages | avg_leaf_density | leaf_fragmentation
|
|
|
|
|
---------+------------+------------+---------------+----------------+------------+-------------+---------------+------------------+--------------------
|
Fix multiple bugs in contrib/pgstattuple's pgstatindex() function.
Dead or half-dead index leaf pages were incorrectly reported as live, as a
consequence of a code rearrangement I made (during a moment of severe brain
fade, evidently) in commit d287818eb514d431.
The index metapage was not counted in index_size, causing that result to
not agree with the actual index size on-disk.
Index root pages were not counted in internal_pages, which is inconsistent
compared to the case of a root that's also a leaf (one-page index), where
the root would be counted in leaf_pages. Aside from that inconsistency,
this could lead to additional transient discrepancies between the reported
page counts and index_size, since it's possible for pgstatindex's scan to
see zero or multiple pages marked as BTP_ROOT, if the root moves due to
a split during the scan. With these fixes, index_size will always be
exactly one page more than the sum of the displayed page counts.
Also, the index_size result was incorrectly documented as being measured in
pages; it's always been measured in bytes. (While fixing that, I couldn't
resist doing some small additional wordsmithing on the pgstattuple docs.)
Including the metapage causes the reported index_size to not be zero for
an empty index. To preserve the desired property that the pgstattuple
regression test results are platform-independent (ie, BLCKSZ configuration
independent), scale the index_size result in the regression tests.
The documentation issue was reported by Otsuka Kenji, and the inconsistent
root page counting by Peter Geoghegan; the other problems noted by me.
Back-patch to all supported branches, because this has been broken for
a long time.
2016-02-18 21:40:35 +01:00
|
|
|
2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | NaN | NaN
|
2013-07-18 20:50:20 +02:00
|
|
|
(1 row)
|
|
|
|
|
|
2011-08-25 06:06:16 +02:00
|
|
|
select pg_relpages('test');
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
0
|
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
|
|
select pg_relpages('test_pkey');
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
1
|
|
|
|
|
(1 row)
|
|
|
|
|
|
2013-07-18 20:50:20 +02:00
|
|
|
select pg_relpages('test_pkey'::text);
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
1
|
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
|
|
select pg_relpages('test_pkey'::name);
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
1
|
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
|
|
select pg_relpages('test_pkey'::regclass);
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
1
|
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
|
|
select pg_relpages(oid) from pg_class where relname = 'test_pkey';
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
1
|
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
|
|
select pg_relpages(relname) from pg_class where relname = 'test_pkey';
|
|
|
|
|
pg_relpages
|
|
|
|
|
-------------
|
|
|
|
|
1
|
|
|
|
|
(1 row)
|
|
|
|
|
|
2012-12-05 08:58:03 +01:00
|
|
|
create index test_ginidx on test using gin (b);
|
|
|
|
|
select * from pgstatginindex('test_ginidx');
|
|
|
|
|
version | pending_pages | pending_tuples
|
|
|
|
|
---------+---------------+----------------
|
2014-01-22 17:51:48 +01:00
|
|
|
2 | 0 | 0
|
2012-12-05 08:58:03 +01:00
|
|
|
(1 row)
|
|
|
|
|
|
