[COMMITTERS] pgsql: Fix some typos and spelling errors in comments

Fix some typos and spelling errors in comments Author: Erik Rijkers Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/130ae4a5478b3b3965779ece1436fa3611aa957f Modified Files -- src/backend/replication/walsender.c | 30 +++--- 1 file

[COMMITTERS] pgsql: Fix behavior of psql's \p to agree with \g, \w, etc.

Fix behavior of psql's \p to agree with \g, \w, etc. In commit e984ef586 I (tgl) simplified the behavior of \p to just print the current query buffer; but Daniel Vérité points out that this made it inconsistent with the behavior of \g and \w. It should print the same thing \g would execute. Fix

[COMMITTERS] pgsql: Doc: clarify behavior of OT_WHOLE_LINE and OT_FILEPIPE psql slas

Doc: clarify behavior of OT_WHOLE_LINE and OT_FILEPIPE psql slash commands. This is another bit of ancient behavior that was documented poorly (in a couple of cases) or not at all (in several others). Discussion: https://postgr.es/m/9b4ea968-753f-4b5f-b46c-d7d3bf7c8...@manitou-mail.org Branch -

[COMMITTERS] pgsql: Document psql's behavior of recalling the previously executed qu

Document psql's behavior of recalling the previously executed query. Various psql slash commands that normally act on the current query buffer will automatically recall and re-use the most recently executed SQL command instead, if the current query buffer is empty. Although this behavior is ancie

[COMMITTERS] pgsql: Remove reinvention of stringify macro.

Remove reinvention of stringify macro. We already have CppAsString2, there's no need for the MSVC support to re-invent a macro to do that (and especially not to inject it in as ugly a way as this). Discussion: https://postgr.es/m/CADkLM=c+hm2rc0tkKgC-ZgrLttHT2KkfppE+BC-=i-xj+7v...@mail.gmail.com