aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/explain.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-04-12 14:03:24 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-04-12 14:03:24 -0400
commit88d934f0387a66ba372643913f99e845d0ea144a (patch)
tree9f517164f9277b24fc43ac579d2631bf829236d5 /src/backend/commands/explain.c
parentdbc60c5593f26dc777a3be032bff4fb4eab1ddd1 (diff)
downloadpostgresql-88d934f0387a66ba372643913f99e845d0ea144a.tar.gz
postgresql-88d934f0387a66ba372643913f99e845d0ea144a.zip
Doc: introduce and document "&zwsp;" for allowing optional line breaks.
We already had a couple of places using zero-width spaces for formatting hackery, and we're going to need more if we ever want the PDF manuals to look decent. But please let's not write hard-coded Unicode escapes. We can avoid that by using a custom entity, which also provides a place to put a teeny bit of documentation about what it is and how to use it. I'd previously posted a patch using "&break;" for this, but on reflection that would be horrible to grep for. Instead let's use "&zwsp;", based on the name of the Unicode symbol ("zero width space"). Discussion: https://postgr.es/m/9326.1581457869@sss.pgh.pa.us
Diffstat (limited to 'src/backend/commands/explain.c')
0 files changed, 0 insertions, 0 deletions