diff options
author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2020-10-27 13:49:19 -0300 |
---|---|---|
committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2020-10-27 13:49:19 -0300 |
commit | 2f0baa244f399ce152fb0da018d7156fdfe8b47d (patch) | |
tree | 3d44807ca79e0907d1cb34bf8a52574123300efc /src/backend/commands | |
parent | 2339038a9b212e3ae846b2330de15c51752b1059 (diff) |
Accept relations of any kind in LOCK TABLE
The restriction that only tables and views can be locked by LOCK TABLE
is quite arbitrary, since the underlying mechanism can lock any relation
type. Drop the restriction so that programs such as pg_dump can lock
all relations they're interested in, preventing schema changes that
could cause a dump to fail after expending much effort.
Backpatch to 9.5.
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Reported-by: Wells Oliver <wells.oliver@gmail.com>
Discussion: https://postgr.es/m/20201021200659.GA32358@alvherre.pgsql
Diffstat (limited to 'src/backend/commands')
-rw-r--r-- | src/backend/commands/lockcmds.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/src/backend/commands/lockcmds.c b/src/backend/commands/lockcmds.c index bb7d9e8239e..d48a15984f3 100644 --- a/src/backend/commands/lockcmds.c +++ b/src/backend/commands/lockcmds.c @@ -88,13 +88,6 @@ RangeVarCallbackForLockTable(const RangeVar *rv, Oid relid, Oid oldrelid, return; /* woops, concurrently dropped; no permissions * check */ - /* Currently, we only allow plain tables to be locked */ - if (relkind != RELKIND_RELATION && relkind != RELKIND_PARTITIONED_TABLE) - ereport(ERROR, - (errcode(ERRCODE_WRONG_OBJECT_TYPE), - errmsg("\"%s\" is not a table", - rv->relname))); - /* * Make note if a temporary relation has been accessed in this * transaction. |