Re: [HACKERS] Guarding against bugs-of-omission in initdb's setup_depend
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Guarding against bugs-of-omission in initdb's setup_depend |
Дата | |
Msg-id | CA+TgmoYSnfnT5hzE=v5H-YrrOBrTAH1yD7XZcA+WDgkDhnM8Bg@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] Guarding against bugs-of-omission in initdb's setup_depend (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Guarding against bugs-of-omission in initdb's setup_depend
|
Список | 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
В списке pgsql-hackers по дате отправления: