mirror of
https://github.com/postgres/postgres.git
synced 2025-04-25 21:42:33 +03:00
b61e6214cf
This commit fixes a set of issues related to the use of the SQL functions in this module when the caller is able to pass down raw page data as input argument: - The page size check was fuzzy in a couple of places, sometimes looking after only a sub-range, but what we are looking for is an exact match on BLCKSZ. After considering a few options here, I have settled down to do a generalization of get_page_from_raw(). Most of the SQL functions already used that, and this is not strictly required if not accessing an 8-byte-wide value from a raw page, but this feels safer in the long run for alignment-picky environment, particularly if a code path begins to access such values. This also reduces the number of strings that need to be translated. - The BRIN function brin_page_items() uses a Relation but it did not check the access method of the opened index, potentially leading to crashes. All the other functions in need of a Relation already did that. - Some code paths could fail on elog(), but we should to use ereport() for failures that can be triggered by the user. Tests are added to stress all the cases that are fixed as of this commit, with some junk raw pages (\set VERBOSITY ensures that this works across all page sizes) and unexpected index types when functions open relations. Author: Michael Paquier, Justin Prysby Discussion: https://postgr.es/m/20220218030020.GA1137@telsasoft.com Backpatch-through: 10
43 lines
1.9 KiB
PL/PgSQL
43 lines
1.9 KiB
PL/PgSQL
-- The gist_page_opaque_info() function prints the page's LSN. Normally,
|
|
-- that's constant 1 (GistBuildLSN) on every page of a freshly built GiST
|
|
-- index. But with wal_level=minimal, the whole relation is dumped to WAL at
|
|
-- the end of the transaction if it's smaller than wal_skip_threshold, which
|
|
-- updates the LSNs. Wrap the tests on gist_page_opaque_info() in the
|
|
-- same transaction with the CREATE INDEX so that we see the LSNs before
|
|
-- they are possibly overwritten at end of transaction.
|
|
BEGIN;
|
|
|
|
-- Create a test table and GiST index.
|
|
CREATE TABLE test_gist AS SELECT point(i,i) p, i::text t FROM
|
|
generate_series(1,1000) i;
|
|
CREATE INDEX test_gist_idx ON test_gist USING gist (p);
|
|
|
|
-- Page 0 is the root, the rest are leaf pages
|
|
SELECT * FROM gist_page_opaque_info(get_raw_page('test_gist_idx', 0));
|
|
SELECT * FROM gist_page_opaque_info(get_raw_page('test_gist_idx', 1));
|
|
SELECT * FROM gist_page_opaque_info(get_raw_page('test_gist_idx', 2));
|
|
|
|
COMMIT;
|
|
|
|
SELECT * FROM gist_page_items(get_raw_page('test_gist_idx', 0), 'test_gist_idx');
|
|
SELECT * FROM gist_page_items(get_raw_page('test_gist_idx', 1), 'test_gist_idx') LIMIT 5;
|
|
|
|
-- gist_page_items_bytea prints the raw key data as a bytea. The output of that is
|
|
-- platform-dependent (endianess), so omit the actual key data from the output.
|
|
SELECT itemoffset, ctid, itemlen FROM gist_page_items_bytea(get_raw_page('test_gist_idx', 0));
|
|
|
|
-- Failure with non-GiST index.
|
|
CREATE INDEX test_gist_btree on test_gist(t);
|
|
SELECT gist_page_items(get_raw_page('test_gist_btree', 0), 'test_gist_btree');
|
|
|
|
-- Failure with incorrect page size
|
|
-- Suppress the DETAIL message, to allow the tests to work across various
|
|
-- page sizes.
|
|
\set VERBOSITY terse
|
|
SELECT gist_page_items_bytea('aaa'::bytea);
|
|
SELECT gist_page_items('aaa'::bytea, 'test_gist_idx'::regclass);
|
|
SELECT gist_page_opaque_info('aaa'::bytea);
|
|
\set VERBOSITY default
|
|
|
|
DROP TABLE test_gist;
|