Skip to content

Commit 235a52c

Browse files
committed
Improve the check for pg_catalog.line data type in pg_upgrade
The pg_upgrade check for pg_catalog.line data type when upgrading from 9.3 had a couple of issues with domains and composite types. Firstly, it triggered false positives for composite types unused in objects with storage. This was enough to trigger an unnecessary pg_upgrade failure: CREATE TYPE line_composite AS (l pg_catalog.line) On the other hand, this only happened with composite types directly on the pg_catalog.line data type, but not with a domain. So this was not detected CREATE DOMAIN line_domain AS pg_catalog.line; CREATE TYPE line_composite_2 AS (l line_domain); unlike the first example. These false positives and inconsistencies are unfortunate, but what's worse we've failed to detected objects using the pg_catalog.line data type through a domain. So we missed cases like this CREATE TABLE t (l line_composite_2); The consequence is clusters broken after a pg_upgrade. This fixes these false positives and false negatives by using the same recursive CTE introduced by eaf900e for sql_identifier. 9.3 did not support domains on composite types, but we can still have multi-level composite types. Backpatch all the way to 9.4, where the format for pg_catalog.line data type changed. Author: Tomas Vondra Backpatch-to: 9.4- Discussion: https://postgr.es/m/16045-673e8fa6b5ace196%40postgresql.org
1 parent 952af24 commit 235a52c

File tree

1 file changed

+29
-1
lines changed

1 file changed

+29
-1
lines changed

contrib/pg_upgrade/version.c

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,14 +127,42 @@ old_9_3_check_for_line_data_type_usage(ClusterInfo *cluster)
127127
DbInfo *active_db = &cluster->dbarr.dbs[dbnum];
128128
PGconn *conn = connectToServer(cluster, active_db->db_name);
129129

130+
/*
131+
* The pg_catalog.line type may be wrapped in a domain or composite
132+
* type, or both (9.3 did not allow domains on composite types, but
133+
* there may be multi-level composite type). To detect these cases
134+
* we need a recursive CTE.
135+
*/
130136
res = executeQueryOrDie(conn,
137+
"WITH RECURSIVE oids AS ( "
138+
/* the pg_catalog.line type itself */
139+
" SELECT 'pg_catalog.line'::pg_catalog.regtype AS oid "
140+
" UNION ALL "
141+
" SELECT * FROM ( "
142+
/* domains on the type */
143+
" WITH x AS (SELECT oid FROM oids) "
144+
" SELECT t.oid FROM pg_catalog.pg_type t, x WHERE typbasetype = x.oid AND typtype = 'd' "
145+
" UNION "
146+
/* composite types containing the type */
147+
" SELECT t.oid FROM pg_catalog.pg_type t, pg_catalog.pg_class c, pg_catalog.pg_attribute a, x "
148+
" WHERE t.typtype = 'c' AND "
149+
" t.oid = c.reltype AND "
150+
" c.oid = a.attrelid AND "
151+
" NOT a.attisdropped AND "
152+
" a.atttypid = x.oid "
153+
" ) foo "
154+
") "
131155
"SELECT n.nspname, c.relname, a.attname "
132156
"FROM pg_catalog.pg_class c, "
133157
" pg_catalog.pg_namespace n, "
134158
" pg_catalog.pg_attribute a "
135159
"WHERE c.oid = a.attrelid AND "
136160
" NOT a.attisdropped AND "
137-
" a.atttypid = 'pg_catalog.line'::pg_catalog.regtype AND "
161+
" a.atttypid IN (SELECT oid FROM oids) AND "
162+
" c.relkind IN ("
163+
CppAsString2(RELKIND_RELATION) ", "
164+
CppAsString2(RELKIND_MATVIEW) ", "
165+
CppAsString2(RELKIND_INDEX) ") AND "
138166
" c.relnamespace = n.oid AND "
139167
/* exclude possible orphaned temp tables */
140168
" n.nspname !~ '^pg_temp_' AND "

0 commit comments

Comments
 (0)