Thread: pgsql: Don't throw an error for LOCK TABLE on a self-referential view.

Don't throw an error for LOCK TABLE on a self-referential view.

LOCK TABLE has complained about "infinite recursion" when applied
to a self-referential view, ever since we made it recurse into views
in v11.  However, that breaks pg_dump's new assumption that it's
okay to lock every relation.  There doesn't seem to be any good
reason to throw an error: if we just abandon the recursion, we've
still satisfied the requirement of locking every referenced relation.

Per bug #16703 from Andrew Bille (via Alexander Lakhin).

Discussion: https://postgr.es/m/16703-e348f58aab3cf6cc@postgresql.org

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/0bdf1ef3d53e42c1c050a9f30b663fe72269a129

Modified Files
--------------
src/backend/commands/lockcmds.c    | 21 ++++++++++++---------
src/test/regress/expected/lock.out |  4 +---
src/test/regress/sql/lock.sql      |  2 +-
3 files changed, 14 insertions(+), 13 deletions(-)