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/[email protected] Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/7dc18c619dac7ddf8af62b4d33e4bd33c7bfb067 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(-)
