Re: Return of "can't paste into psql" issue

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Return of "can't paste into psql" issue
Date: 2013-07-18 12:57:33
Message-ID: CAHyXU0wjNPvG=OrGf0EY1yRY0Pc8OUq6LY-B_J7G+VDTf+nNEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 17, 2013 at 6:30 PM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> So, an even more practical workaround (I've been using cat | psql), but
>> still a mysterious issue.
>
> As a workaround you might try \e with EDITOR=emacs or some of the other
> solutions you've been pasting, maybe even cat, so that you can switch
> that readline-completion-bug-free environment for just that paste?

Well, I use \e=vim and it works fine. But, sometimes you forget and
the results can be destructive to the database. I messed around for a
little bit with the tab completion callback routine yesterday and I
now believe that's not the issue. It only fires when you tab AFAICT
-- so the problem is in the readline function itself which reduces the
set of solutions somewhat -- either you run it or you don't.

One thing that could solve a lot of issues would be to disable
readline when inside a dollar quote etc.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2013-07-18 12:59:23 Re: Return of "can't paste into psql" issue
Previous Message Robert Haas 2013-07-18 12:46:48 getting rid of SnapshotNow