From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pasting a lot of commands to psql |
Date: | 2016-07-07 20:09:02 |
Message-ID: | 4f041666-e2e2-8c3b-57a9-050d0bacabf0@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/7/2016 12:48 PM, Alvaro Herrera wrote:
>> Agreed. I've looked at this problem extensively and concur that
>> >readline is the culprit; I don't think there's any solution on our end
>> >besides filing a bug with the readline. I also agree with the
>> >upthread suggestion that the best workaround today is to \e into a
>> >non-readline based editor (vim qualifies). Having said that, at least
>> >on linux/gnome, very long pastes can cause severe performance issues
>> >as well. So for large pastes I go with psql -f.
> Hmm, I was doing megabyte-long pastes (longest one over 5 MB) just a few
> weeks ago and was pleasantly surprised to discover that they worked just
> fine with no noticeable performance problem. I was pasting skype logs
> directly from the Linux skype client window into an xterm running cat,
> with obviously no readline involved.
yeah, long pastes generally work fine with ssh sessions, too, using ssh
clients like putty or securecrt.
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2016-07-07 20:31:26 | Re: pasting a lot of commands to psql |
Previous Message | Alvaro Herrera | 2016-07-07 19:48:50 | Re: pasting a lot of commands to psql |