From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Document that dependency tracking doesn't consider function bodi |
Date: | 2016-06-22 00:08:34 |
Message-ID: | E1bFVic-0005SI-C7@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Document that dependency tracking doesn't consider function bodies.
If there's anyplace in our SGML docs that explains this behavior, I can't
find it right at the moment. Add an explanation in "Dependency Tracking"
which seems like the authoritative place for such a discussion. Per
gripe from Michelle Schwan.
While at it, update this section's example of a dependency-related
error message: they last looked like that in 8.3. And remove the
explanation of dependency updates from pre-7.3 installations, which
is probably no longer worth anybody's brain cells to read.
The bogus error message example seems like an actual documentation bug,
so back-patch to all supported branches.
Discussion: <20160620160047(dot)5792(dot)49827(at)wrigleys(dot)postgresql(dot)org>
Branch
------
REL9_2_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/85743887e847b187bb16ec1f0ca3b967bc124223
Modified Files
--------------
doc/src/sgml/ddl.sgml | 57 ++++++++++++++++++++++++++++++++++++---------------
1 file changed, 40 insertions(+), 17 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2016-06-22 00:24:06 | pgsql: Update comment about allowing GUCs to change scanning. |
Previous Message | Tom Lane | 2016-06-21 22:38:30 | pgsql: Refactor planning of projection steps that don't need a Result p |