Re: erroneous restore into pg_catalog schema
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Erik Rijkers <er@xs4all.nl>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, pgsql-hackers@postgresql.org, Robert Haas <robertmhaas@gmail.com>, Kohei KaiGai <kaigai@kaigai.gr.jp>
Date: 2013-01-14T17:28:58Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > The attached patch seems to work: > alvherre=# create table pg_catalog.foo (a int); > ERROR: permission denied for schema pg_catalog > I notice that contrib/adminpack now fails, though (why doesn't this > module have a regression test?): > alvherre=# create extension adminpack; > ERROR: permission denied for schema pg_catalog Um. I knew that that module's desire to shove stuff into pg_catalog would bite us someday. But now that I think about it, I'm pretty sure I recall discussions to the effect that there are other third-party modules doing similar things. Anyway, this seems to answer Robert's original question about why relations were special-cased: there are too many special cases around this behavior. I think we should seriously consider just reverting a475c6036. regards, tom lane
Commits
-
Extend and improve use of EXTRA_REGRESS_OPTS.
- 4ae5ee6c9b4d 9.3.0 cited
-
Remove misplaced sanity check from heap_create().
- a475c6036752 9.3.0 cited
-
Silently ignore any nonexistent schemas that are listed in search_path.
- 880bfc3287dd 9.2.0 cited