Prevent adding relations to a concurrently dropped schema.
In the previous coding, it was possible for a relation to be created
via CREATE TABLE, CREATE VIEW, CREATE SEQUENCE, CREATE FOREIGN TABLE,
etc. in a schema while that schema was meanwhile being concurrently
dropped. This led to a pg_class entry with an invalid relnamespace
value. The same problem could occur if a relation was moved using
ALTER .. SET SCHEMA while the target schema was being concurrently
dropped. This patch prevents both of those scenarios by locking the
schema to which the relation is being added using AccessShareLock,
which conflicts with the AccessExclusiveLock taken by DROP.
As a desirable side effect, this also prevents the use of CREATE OR
REPLACE VIEW to queue for an AccessExclusiveLock on a relation on which
you have no rights: that will now fail immediately with a permissions
error, before trying to obtain a lock.
We need similar protection for all other object types, but as everything
other than relations uses a slightly different set of code paths, I'm
leaving that for a separate commit.
Original complaint (as far as I could find) about CREATE by Nikhil
Sontakke; risk for ALTER .. SET SCHEMA pointed out by Tom Lane;
further details by Dan Farina; patch by me; review by Hitoshi Harada.
src/backend/catalog/namespace.c | 122 ++++++++++++++++++++++++++++++++---
src/backend/commands/tablecmds.c | 14 +++--
src/backend/commands/typecmds.c | 3 +-
src/backend/commands/view.c | 36 +++++------
src/backend/executor/execMain.c | 8 ++-
src/backend/parser/parse_utilcmd.c | 30 ++++-----
src/include/catalog/namespace.h | 4 +-
7 files changed, 158 insertions(+), 59 deletions(-)
pgsql-committers by date
|Next:||From: Peter Eisentraut||Date: 2012-01-16 18:10:06|
|Subject: pgsql: psql: Fix memory leak|
|Previous:||From: Fujii Masao||Date: 2012-01-16 01:44:14|
|Subject: Re: pgsql: Correctly initialise shared
recoveryLastRecPtr in recovery.|