Re: failure of \e in psql - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: failure of \e in psql
Date
Msg-id 199911120607.BAA01516@candle.pha.pa.us
Whole thread Raw
In response to Re: failure of \e in psql  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: failure of \e in psql  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
List pgsql-hackers
> On 1999-11-11, Bruce Momjian mentioned:
> 
> > I see that \e no longer works as expected:
> > 
> >     test=> select * from pg_class;
> >     ...
> >     test=> \e
> > 
> > and in the editor, the query is not appearing.  The 'select' query
> > should appear in the editor because I have not entered a non-backslash
> > command to clear the query buffer.
> 
> Well, once you send it, it's sent and gone. You have to edit it before you
> send it. I guess I'm not following you. Of course you should somehow be
> able to re-edit the previous query. Hmm.

Peter, before I go hunting around, can you tell me any other things psql
used to do that it doesn't do anymore?

We had hand-tuned psql over the years, and it would be good to know what
features no longer exist so we can decide if they are needed.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] Slow - grindingly slow - query
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] compression in LO and other fields