From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Doc: undo mistaken adjustment to LOCK TABLE docs in back branche |
Date: | 2020-11-06 17:15:49 |
Message-ID: | E1kb5L3-0004Al-Ce@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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
Branch
------
REL9_5_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/8b4121903c2d7deca4a7041af791ede46597f9dd
Modified Files
--------------
doc/src/sgml/ref/lock.sgml | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-11-06 21:18:35 | pgsql: Revert "Accept relations of any kind in LOCK TABLE". |
Previous Message | Fujii Masao | 2020-11-06 17:09:28 | pgsql: pg_prewarm: make autoprewarm leader use standard SIGHUP and SIGT |