diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-06 12:14:55 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-06 12:14:55 -0500 |
| commit | 8b4121903c2d7deca4a7041af791ede46597f9dd (patch) | |
| tree | 534bf22eb1e6369cccd2fa4487de275fff64f616 /src/backend/access/gist/gistbuild.c | |
| parent | 77df80cf691af9270ef52d860b5615d6d0a7afbc (diff) | |
| download | postgresql-8b4121903c2d7deca4a7041af791ede46597f9dd.tar.gz postgresql-8b4121903c2d7deca4a7041af791ede46597f9dd.zip | |
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/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions