aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.h
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-12-01 12:06:31 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-12-01 12:06:31 -0500
commit83884682f4df96184549b91869a1cf79dafb4f94 (patch)
tree2d152ed94c9fac1071e68a76456e4cfe074dfab6 /contrib/postgres_fdw/postgres_fdw.h
parent89d1c15d64602b0c27ed87c717f586ddf6cf310d (diff)
downloadpostgresql-83884682f4df96184549b91869a1cf79dafb4f94.tar.gz
postgresql-83884682f4df96184549b91869a1cf79dafb4f94.zip
psql: include intra-query "--" comments in what's sent to the server.
psql's lexer has historically deleted dash-dash (single-line) comments from what's collected and sent to the server. This is inconsistent with what it does for slash-star comments, and people have complained before that they wish such comments would be captured in the server log. Undoing the decision completely seems like too big a behavioral change, however. In particular, comments on lines preceding the start of a query are generally not thought of as being part of that query. What we can do to improve the situation is to capture comments that are clearly *within* a query, that is after the first non-whitespace, non-comment token but before the query's ending semicolon or backslash command. This is a nearly trivial code change, and it affects only a few regression test results. (It is tempting to try to apply the same rule to slash-star comments. But it's hard to see how to do that without getting strange history behavior for comments that cross lines, especially if the user then starts a new query on the same line as the star-slash. In view of the lack of complaints, let's leave that case alone.) Discussion: https://postgr.es/m/CAJcOf-cAdMVr7azeYR7nWKsNp7qhORzc84rV6d7m7knG5Hrtsw@mail.gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.h')
0 files changed, 0 insertions, 0 deletions