The pg_overexplain documentation previously used the <literal> tag for
some file names, struct names, and commands. Update the markup to
use the more appropriate tags: <filename>, <structname>, and <command>.
Backpatch to v18, where pg_overexplain was introduced.
Author: Fujii Masao <
[email protected]>
Reviewed-by: Shixin Wang <[email protected]>
Reviewed-by: Chao Li <[email protected]>
Discussion: https://postgr.es/m/CAHGQGwEyYUzz0LjBV_fMcdwU3wgmu0NCoT+JJiozPa8DG6eeog@mail.gmail.com
Backpatch-through: 18
The <literal>DEBUG</literal> option displays miscellaneous information from
the plan tree that is not normally shown because it is not expected to be
of general interest. For each individual plan node, it will display the
The <literal>DEBUG</literal> option displays miscellaneous information from
the plan tree that is not normally shown because it is not expected to be
of general interest. For each individual plan node, it will display the
- following fields. See <literal>Plan</literal> in
- <literal>nodes/plannodes.h</literal> for additional documentation of these
+ following fields. See <structname>Plan</structname> in
+ <filename>nodes/plannodes.h</filename> for additional documentation of these
<para>
Once per query, the <literal>DEBUG</literal> option will display the
<para>
Once per query, the <literal>DEBUG</literal> option will display the
- following fields. See <literal>PlannedStmt</literal> in
- <literal>nodes/plannodes.h</literal> for additional detail.
+ following fields. See <structname>PlannedStmt</structname> in
+ <filename>nodes/plannodes.h</filename> for additional detail.
<listitem>
<para>
<literal>Flags</literal>. A comma-separated list of Boolean structure
<listitem>
<para>
<literal>Flags</literal>. A comma-separated list of Boolean structure
- member names from the <literal>PlannedStmt</literal> that are set to
+ member names from the <structname>PlannedStmt</structname> that are set to
<literal>true</literal>. It covers the following structure members:
<literal>hasReturning</literal>, <literal>hasModifyingCTE</literal>,
<literal>canSetTag</literal>, <literal>transientPlan</literal>,
<literal>true</literal>. It covers the following structure members:
<literal>hasReturning</literal>, <literal>hasModifyingCTE</literal>,
<literal>canSetTag</literal>, <literal>transientPlan</literal>,
table entry (e.g. <literal>relation</literal>,
<literal>subquery</literal>, or <literal>join</literal>), followed by the
contents of various range table entry fields that are not normally part of
table entry (e.g. <literal>relation</literal>,
<literal>subquery</literal>, or <literal>join</literal>), followed by the
contents of various range table entry fields that are not normally part of
- <literal>EXPLAIN</literal> output. Some of these fields are only displayed
+ <command>EXPLAIN</command> output. Some of these fields are only displayed
for certain kinds of range table entries. For example,
<literal>Eref</literal> is displayed for all types of range table entries,
but <literal>CTE Name</literal> is displayed only for range table entries
for certain kinds of range table entries. For example,
<literal>Eref</literal> is displayed for all types of range table entries,
but <literal>CTE Name</literal> is displayed only for range table entries
<para>
For more information about range table entries, see the definition of
<para>
For more information about range table entries, see the definition of
- <literal>RangeTblEntry</literal> in <literal>nodes/parsenodes.h</literal>.
+ <structname>RangeTblEntry</structname> in <filename>nodes/parsenodes.h</filename>.