diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-06 12:14:36 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-06 12:14:36 -0500 |
commit | 33862cb9c13a9d5c53e887bea4909415e73be634 (patch) | |
tree | 51cc682d86b01a7b984556aab43be6381e1548bf /src/backend/commands/lockcmds.c | |
parent | 9d878d7fee789d79afb846e401e56a65dd23a0f4 (diff) |
Doc: undo mistaken adjustment to LOCK TABLE docs in back branches.
Commits 59ab4ac32 et al mistakenly copied-and-pasted some text about
how LOCK on a view recurses to referenced tables into pre-v11 branches,
which in fact don't do that. Undo that, and instead state clearly
that they don't. (I also chose to add a note that this behavior
changed in v11. We usually don't back-patch such statements, but
since it's easy to add the warning now, might as well.)
Noted while considering followup fixes for bug #16703.
Discussion: https://postgr.es/m/16703-e348f58aab3cf6cc@postgresql.org
Diffstat (limited to 'src/backend/commands/lockcmds.c')
0 files changed, 0 insertions, 0 deletions