mirror of
https://github.com/postgres/postgres.git
synced 2025-05-12 16:21:30 +03:00
c08d82f38e
The contrib extensions pageinspect, pg_visibility and pgstattuple only work against regular relations which have storage. They don't work against foreign tables, partitioned (parent) tables, views, et al. Add checks to the user-callable functions to return a useful error message to the user if they mistakenly pass an invalid relation to a function which doesn't accept that kind of relation. In passing, improve some of the existing checks to use ereport() instead of elog(), add a function to consolidate common checks where appropriate, and add some regression tests. Author: Amit Langote, with various changes by me Reviewed by: Michael Paquier and Corey Huinker Discussion: https://postgr.es/m/ab91fd9d-4751-ee77-c87b-4dd704c1e59c@lab.ntt.co.jp
40 lines
1.5 KiB
SQL
40 lines
1.5 KiB
SQL
CREATE EXTENSION pageinspect;
|
|
|
|
CREATE TABLE test1 (a int, b int);
|
|
INSERT INTO test1 VALUES (16777217, 131584);
|
|
|
|
VACUUM test1; -- set up FSM
|
|
|
|
-- The page contents can vary, so just test that it can be read
|
|
-- successfully, but don't keep the output.
|
|
|
|
SELECT octet_length(get_raw_page('test1', 'main', 0)) AS main_0;
|
|
SELECT octet_length(get_raw_page('test1', 'main', 1)) AS main_1;
|
|
|
|
SELECT octet_length(get_raw_page('test1', 'fsm', 0)) AS fsm_0;
|
|
SELECT octet_length(get_raw_page('test1', 'fsm', 1)) AS fsm_1;
|
|
|
|
SELECT octet_length(get_raw_page('test1', 'vm', 0)) AS vm_0;
|
|
SELECT octet_length(get_raw_page('test1', 'vm', 1)) AS vm_1;
|
|
|
|
SELECT octet_length(get_raw_page('xxx', 'main', 0));
|
|
SELECT octet_length(get_raw_page('test1', 'xxx', 0));
|
|
|
|
SELECT get_raw_page('test1', 0) = get_raw_page('test1', 'main', 0);
|
|
|
|
SELECT tuple_data_split('test1'::regclass, t_data, t_infomask, t_infomask2, t_bits)
|
|
FROM heap_page_items(get_raw_page('test1', 0));
|
|
|
|
SELECT * FROM fsm_page_contents(get_raw_page('test1', 'fsm', 0));
|
|
|
|
DROP TABLE test1;
|
|
|
|
-- check that using any of these functions with a partitioned table would fail
|
|
create table test_partitioned (a int) partition by range (a);
|
|
select get_raw_page('test_partitioned', 0); -- error about partitioned table
|
|
|
|
-- a regular table which is a member of a partition set should work though
|
|
create table test_part1 partition of test_partitioned for values from ( 1 ) to (100);
|
|
select get_raw_page('test_part1', 0); -- get farther and error about empty table
|
|
drop table test_partitioned;
|