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

2020-11-05 Thread Tom Lane
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. Ther

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

2020-11-05 Thread Tom Lane
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. Ther

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

2020-11-05 Thread Tom Lane
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. Ther

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

2020-11-05 Thread Tom Lane
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. Ther