Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit07b3908

Browse files
committed
Fix pg_dump's handling of dependencies for custom opclasses.
Since pg_dump doesn't treat the member operators and functions of operatorclasses/families (that is, the pg_amop and pg_amproc entries, not theunderlying operators/functions) as separate dumpable objects, it missedtheir dependency information. I think this was safe when the code wasdesigned, because the default object sorting rule emits operators andfunctions before opclasses, and there were no dependency types that couldmess that up. However, the introduction of range types in 9.2 broke it:now a type can have a dependency on an opclass, allowing dependency rulesto push the opclass before the type and hence before custom operators.Lacking any information showing that it shouldn't do so, pg_dump emittedthe objects in the wrong order.Fix by teaching getDependencies() to translate pg_depend entries forpg_amop/amproc rows to look like dependencies for their parent opfamily.I added a regression test for this in HEAD/v12, but not further back;life is too short to fight with 002_pg_dump.pl.Per bug #15934 from Tom Gottfried. Back-patch to all supported branches.Discussion:https://postgr.es/m/15934-58b8c8ab7a09ea15@postgresql.org
1 parentf140007 commit07b3908

File tree

2 files changed

+62
-2
lines changed

2 files changed

+62
-2
lines changed

‎src/bin/pg_dump/pg_dump.c

Lines changed: 33 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17911,14 +17911,45 @@ getDependencies(Archive *fout)
1791117911
query = createPQExpBuffer();
1791217912

1791317913
/*
17914+
* Messy query to collect the dependency data we need. Note that we
17915+
* ignore the sub-object column, so that dependencies of or on a column
17916+
* look the same as dependencies of or on a whole table.
17917+
*
1791417918
* PIN dependencies aren't interesting, and EXTENSION dependencies were
1791517919
* already processed by getExtensionMembership.
1791617920
*/
1791717921
appendPQExpBufferStr(query, "SELECT "
1791817922
"classid, objid, refclassid, refobjid, deptype "
1791917923
"FROM pg_depend "
17920-
"WHERE deptype != 'p' AND deptype != 'e' "
17921-
"ORDER BY 1,2");
17924+
"WHERE deptype != 'p' AND deptype != 'e'\n");
17925+
17926+
/*
17927+
* Since we don't treat pg_amop entries as separate DumpableObjects, we
17928+
* have to translate their dependencies into dependencies of their parent
17929+
* opfamily. Ignore internal dependencies though, as those will point to
17930+
* their parent opclass, which we needn't consider here (and if we did,
17931+
* it'd just result in circular dependencies). Also, "loose" opfamily
17932+
* entries will have dependencies on their parent opfamily, which we
17933+
* should drop since they'd likewise become useless self-dependencies.
17934+
* (But be sure to keep deps on *other* opfamilies; see amopsortfamily.)
17935+
*/
17936+
appendPQExpBufferStr(query, "UNION ALL\n"
17937+
"SELECT 'pg_opfamily'::regclass AS classid, amopfamily AS objid, refclassid, refobjid, deptype "
17938+
"FROM pg_depend d, pg_amop o "
17939+
"WHERE deptype NOT IN ('p', 'e', 'i') AND "
17940+
"classid = 'pg_amop'::regclass AND objid = o.oid "
17941+
"AND NOT (refclassid = 'pg_opfamily'::regclass AND amopfamily = refobjid)\n");
17942+
17943+
/* Likewise for pg_amproc entries */
17944+
appendPQExpBufferStr(query, "UNION ALL\n"
17945+
"SELECT 'pg_opfamily'::regclass AS classid, amprocfamily AS objid, refclassid, refobjid, deptype "
17946+
"FROM pg_depend d, pg_amproc p "
17947+
"WHERE deptype NOT IN ('p', 'e', 'i') AND "
17948+
"classid = 'pg_amproc'::regclass AND objid = p.oid "
17949+
"AND NOT (refclassid = 'pg_opfamily'::regclass AND amprocfamily = refobjid)\n");
17950+
17951+
/* Sort the output for efficiency below */
17952+
appendPQExpBufferStr(query, "ORDER BY 1,2");
1792217953

1792317954
res = ExecuteSqlQuery(fout, query->data, PGRES_TUPLES_OK);
1792417955

‎src/bin/pg_dump/t/002_pg_dump.pl

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1571,6 +1571,35 @@
15711571
unlike => { exclude_dump_test_schema => 1, },
15721572
},
15731573
1574+
# verify that a custom operator/opclass/range type is dumped in right order
1575+
'CREATE OPERATOR CLASS dump_test.op_class_custom' => {
1576+
create_order => 74,
1577+
create_sql => 'CREATE OPERATOR dump_test.~~ (
1578+
PROCEDURE = int4eq,
1579+
LEFTARG = int,
1580+
RIGHTARG = int);
1581+
CREATE OPERATOR CLASS dump_test.op_class_custom
1582+
FOR TYPE int USING btree AS
1583+
OPERATOR 3 dump_test.~~;
1584+
CREATE TYPE dump_test.range_type_custom AS RANGE (
1585+
subtype = int,
1586+
subtype_opclass = dump_test.op_class_custom);',
1587+
regexp => qr/^
1588+
\QCREATE OPERATOR dump_test.~~ (\E\n.+
1589+
\QCREATE OPERATOR FAMILY dump_test.op_class_custom USING btree;\E\n.+
1590+
\QCREATE OPERATOR CLASS dump_test.op_class_custom\E\n\s+
1591+
\QFOR TYPE integer USING btree FAMILY dump_test.op_class_custom AS\E\n\s+
1592+
\QOPERATOR 3 dump_test.~~(integer,integer);\E\n.+
1593+
\QCREATE TYPE dump_test.range_type_custom AS RANGE (\E\n\s+
1594+
\Qsubtype = integer,\E\n\s+
1595+
\Qsubtype_opclass = dump_test.op_class_custom\E\n
1596+
\Q);\E
1597+
/xms,
1598+
like =>
1599+
{%full_runs,%dump_test_schema_runs, section_pre_data => 1, },
1600+
unlike => { exclude_dump_test_schema => 1, },
1601+
},
1602+
15741603
'CREATE OPERATOR CLASS dump_test.op_class_empty' => {
15751604
create_order => 89,
15761605
create_sql => 'CREATE OPERATOR CLASS dump_test.op_class_empty

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp