Re: erroneous restore into pg_catalog schema
От | Tom Lane |
---|---|
Тема | Re: erroneous restore into pg_catalog schema |
Дата | |
Msg-id | 7408.1368466857@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: erroneous restore into pg_catalog schema (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: erroneous restore into pg_catalog schema
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, May 13, 2013 at 1:03 PM, Andres Freund <andres@2ndquadrant.com> wrote: >> Why don't we just prohibit deletion/modification for anything below >> FirstNormalObjectId instead of using the schema as a restriction? Then >> we can allow creation for tables as well. > We currently do, but that led to problems with $SUBJECT. AFAIR there are no code restrictions based on OID value. We've got restrictions based on things being in pg_catalog or not, and we've got restrictions based on things being marked pinned in pg_depend. Looking at the OID range might be a reasonable proxy for pinned-ness, though, and it would certainly be a lot cheaper than a lookup in pg_depend. regards, tom lane
В списке pgsql-hackers по дате отправления: