From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Allow noise semicolons ending psql \sf, \ef, \sv, \ev commands. |
Date: | 2024-01-10 19:20:15 |
Message-ID: | E1rNe7b-000oFn-QD@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Allow noise semicolons ending psql \sf, \ef, \sv, \ev commands.
Many psql backslash commands tolerate trailing semicolons, even
though that's not part of the official syntax. These did not.
They tried to, by passing semicolon = true to psql_scan_slash_option,
but that function ignored this parameter in OT_WHOLE_LINE mode.
Teach it to do the right thing, and remove the now-duplicative
logic in exec_command_help.
Discussion: https://postgr.es/m/2012251.1704746912@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/390298f0806588ceb131dd47760208bd2cd6298f
Modified Files
--------------
src/bin/psql/command.c | 17 +++++------------
src/bin/psql/psqlscanslash.l | 21 +++++++++++++++++++--
src/test/regress/expected/psql.out | 2 +-
src/test/regress/sql/psql.sql | 2 +-
4 files changed, 26 insertions(+), 16 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-01-10 23:09:39 | pgsql: Restore initdb's old behavior of always setting the lc_xxx GUCs. |
Previous Message | Tom Lane | 2024-01-10 18:51:44 | pgsql: Fix Asserts in calc_non_nestloop_required_outer(). |