aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/arrayfuncs.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2023-07-05 10:02:15 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2023-07-05 10:02:15 +0300
commit5e8068f04e13e12c182eca3e64ac4377e0c93a5d (patch)
tree5bac79fae6ed6250dd218f0f272169b39542cfd0 /src/backend/utils/adt/arrayfuncs.c
parenta77d39d5f4b97c7d08e6786429d69eae5baec48e (diff)
downloadpostgresql-5e8068f04e13e12c182eca3e64ac4377e0c93a5d.tar.gz
postgresql-5e8068f04e13e12c182eca3e64ac4377e0c93a5d.zip
Change example in pgindent README on "/*-----" comments.
Most, but not all, of our "/*----" style comments have an end-guard line with dashes at the end of the comment. However, pgindent doesn't care about the end-guards, so they mostly just waste screen space. Going forward, let's not require end-guards. Remove a broken end-guard in a comment in walsender.c that led me to think about this. Remove the end guard from another comment in walsender.c for consistency, so that we use the same style in all comments in the file. However, we have thousands of existing "/*----" comments the repository, so it's not worth the code churn to change them all. Discussion: https://www.postgresql.org/message-id/fb083c91-d490-3b65-25f3-05e9118b6b0d%40iki.fi
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions