aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-04-17 20:50:26 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-04-17 20:50:40 -0400
commit737d69ffc3cfb2e093975411c1becd65ad029478 (patch)
treea4ea21ea7947db7c872509b7620fe9afb3ce9595 /src/backend/executor/nodeModifyTable.c
parent6741cfa5964768279a13e01e46931664fe0903a4 (diff)
downloadpostgresql-737d69ffc3cfb2e093975411c1becd65ad029478.tar.gz
postgresql-737d69ffc3cfb2e093975411c1becd65ad029478.zip
Doc: revise formatting of function/operator tables.
The table layout ideas proposed in commit e894c6183 were not as widely popular as I'd hoped. After discussion, we've settled on a layout that's effectively a single-column table with cell contents much like a <varlistentry> description of the function or operator; though we're not actually using <varlistentry>, because it'd add way too much vertical space. Instead the effect is accomplished using line-break processing instructions to separate the description and example(s), plus CSS or FO customizations to produce indentation of all but the first line in each cell. While technically this is a bit grotty, it does have the advantage that we won't need to write nearly as much boilerplate markup. This patch updates tables 9.30, 9.31, and 9.33 (which were touched by the previous patch) to the revised style, and additionally converts table 9.10. A lot of work still remains to do, but hopefully it won't be too controversial. Thanks to Andrew Dunstan, Pierre Giraud, Robert Haas, Alvaro Herrera, David Johnston, Jonathan Katz, Isaac Morland for valuable ideas. Discussion: https://postgr.es/m/8691.1586798003@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions