Re: Guarding against bugs-of-omission in initdb's setup_depend
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-06-22T20:35:34Z
Lists: pgsql-hackers
On Thu, Jun 22, 2017 at 2:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > While thinking about something else, it started to bother me that > initdb's setup_depend() function knows exactly which catalogs might > contain pinnable objects. It is not very hard to imagine that somebody > might add a DATA() line to, say, pg_transform.h and expect that the > represented object could not get dropped. Well, tain't so, because > setup_depend() doesn't collect OIDs from there. > > So I'm thinking about adding a regression test case, say in dependency.sql, > that looks for unpinned objects with OIDs in the hand-assigned range, > along the lines of this prototype code: I don't have specific thoughts, but I like the general idea. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Add testing to detect errors of omission in "pin" dependency creation.
- 8be8510cf89d 10.0 landed