mirror of
https://github.com/hanzoai/postgres.git
synced 2026-10-30 18:33:07 +00:00
Tom Lane
7c42a98453
btree_gist's gist_inet_ops and gist_cidr_ops opclasses are
fundamentally broken: they rely on an approximate representation of
the inet values and hence sometimes miss rows they should return.
We want to eventually get rid of them altogether, but as the first
step on that journey, we should mark them not-opcdefault.
To do that, roll up the preceding deltas since 1.2 into a new base
script btree_gist--1.9.sql. This will allow installing 1.9 without
going through a transient situation where gist_inet_ops and
gist_cidr_ops are marked as opcdefault; trying to create them that
way will fail if there's already a matching default opclass in the
core system. Additionally provide btree_gist--1.8--1.9.sql, so
that a database that's been pg_upgraded from an older version can
be migrated to 1.9.
I noted along the way that commit 89786751f had missed marking the
gist_bool_ops support functions as PARALLEL SAFE. While that probably
has little harmful effect (since AFAIK we don't check that when
calling index support functions), this seems like a good time to make
things consistent.
Readers will also note that I removed the former habit of installing
some opclass operators/functions with ALTER OPERATOR FAMILY, instead
just rolling them all into the CREATE OPERATOR CLASS steps. The
comment in btree_gist--1.2.sql that it's necessary to use ALTER for
pg_upgrade reproducibility has been obsolete since we invented the
amadjustmembers infrastructure. Nowadays, gistadjustmembers will
force all operators and non-required support functions to have "soft"
opfamily dependencies, regardless of whether they are installed by
CREATE or ALTER.
Author: Tom Lane <[email protected]>
Reviewed-by: Matthias van de Meent <[email protected]>
Reviewed-by: Heikki Linnakangas <[email protected]>
Discussion: https://postgr.es/m/[email protected]
41 lines
1.6 KiB
PL/PgSQL
41 lines
1.6 KiB
PL/PgSQL
/* contrib/btree_gist/btree_gist--1.8--1.9.sql */
|
|
|
|
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
|
|
\echo Use "ALTER EXTENSION btree_gist UPDATE TO '1.9'" to load this file. \quit
|
|
|
|
--
|
|
-- Mark gist_inet_ops and gist_cidr_ops opclasses as non-default.
|
|
-- This is the first step on the way to eventually removing them.
|
|
--
|
|
-- There's no SQL command for this, so fake it with a manual update on
|
|
-- pg_opclass.
|
|
--
|
|
DO LANGUAGE plpgsql
|
|
$$
|
|
DECLARE
|
|
my_schema pg_catalog.text := pg_catalog.quote_ident(pg_catalog.current_schema());
|
|
old_path pg_catalog.text := pg_catalog.current_setting('search_path');
|
|
BEGIN
|
|
-- for safety, transiently set search_path to just pg_catalog+pg_temp
|
|
PERFORM pg_catalog.set_config('search_path', 'pg_catalog, pg_temp', true);
|
|
|
|
UPDATE pg_catalog.pg_opclass
|
|
SET opcdefault = false
|
|
WHERE opcmethod = (SELECT oid FROM pg_catalog.pg_am WHERE amname = 'gist') AND
|
|
opcname IN ('gist_inet_ops', 'gist_cidr_ops') AND
|
|
opcnamespace = my_schema::pg_catalog.regnamespace;
|
|
|
|
PERFORM pg_catalog.set_config('search_path', old_path, true);
|
|
END
|
|
$$;
|
|
|
|
|
|
-- Fix parallel-safety markings overlooked in btree_gist--1.6--1.7.sql.
|
|
ALTER FUNCTION gbt_bool_consistent(internal, bool, smallint, oid, internal) PARALLEL SAFE;
|
|
ALTER FUNCTION gbt_bool_compress(internal) PARALLEL SAFE;
|
|
ALTER FUNCTION gbt_bool_fetch(internal) PARALLEL SAFE;
|
|
ALTER FUNCTION gbt_bool_penalty(internal, internal, internal) PARALLEL SAFE;
|
|
ALTER FUNCTION gbt_bool_picksplit(internal, internal) PARALLEL SAFE;
|
|
ALTER FUNCTION gbt_bool_union(internal, internal) PARALLEL SAFE;
|
|
ALTER FUNCTION gbt_bool_same(gbtreekey2, gbtreekey2, internal) PARALLEL SAFE;
|