From: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
---|---|
To: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | psql behavior change on upgrade from version 12.x to 13.1 |
Date: | 2021-02-09 18:55:31 |
Message-ID: | 7CCA6956-D22C-4E4F-B7B4-A450A062BF59@yugabyte.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Using a MacBook Pro with the current Big Sur—Version 11.2 (20D64).
I just upgraded to PostgreSQL 13.1. (Earlier, I was on 12.x.) Using psql, the behavior of ordinary copy-and-paste has change dramatically, and for the worse, w.r.t. Version 12.
HAS ANYBODY ELSE SEEN WHAT I REPORT BELOW?
First observation
Now, when I copy a single line SQL command, terminated with semicolon and newline from the Text Edit app (with Command-C or the menu item) and then paste it into psql (with Command-V or the menu item), the newline isn't respected. I have to hit the return key by hand to see the effect. Moreover, the pasted line has a highlighted background.
Second observation
When I copy _several_ lines of SQL commands from the Text Edit app and then paste them into psql, none of the newlines are respected. (I still get the strange highlight.) Now when I hit the return key, I get errors like this:
\i: extra argument "<the text of the line>" ignored
for every single line.
This makes a standard working practice that my fingers have learned over decades suddenly completely unusable.
NOTE: the \i metacommand still works as it always did.
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Förster | 2021-02-09 19:11:02 | Re: psql behavior change on upgrade from version 12.x to 13.1 |
Previous Message | Adrian Klaver | 2021-02-09 17:58:15 | Re: How to I select value of GUC that has - in its name? |