aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-11-02 12:51:46 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-11-02 12:51:46 +0200
commit8ef2a5afdf8ec9e4c8b28a7042c9508eb6161671 (patch)
treeab8b1b7d0c180d9aa9871657d030855c27b7f28b /src/backend/access/transam/commit_ts.c
parent90d8f1b1826ce076a502a43fe7c88423b46c6349 (diff)
downloadpostgresql-8ef2a5afdf8ec9e4c8b28a7042c9508eb6161671.tar.gz
postgresql-8ef2a5afdf8ec9e4c8b28a7042c9508eb6161671.zip
doc: Mention UNION/ORDER BY etc. keywords in section headers.
Most of the section and sub-section headers in the Queries chapter have the keywords literally stated, but neither "Sorting Rows" nor "Combining Rows" did. There's no rule that they must be, but it seems like a good practice. The keywords will ring a bell to anyone with with even a little bit of SQL experience. David G. Johnston, per suggestion by bilge@scriptfusion.com Discussion: https://www.postgresql.org/message-id/159981394174.31338.7014519396749859167%40wrigleys.postgresql.org
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions