Re: psql and \p\g - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: psql and \p\g
Date
Msg-id 199911112150.QAA16006@candle.pha.pa.us
Whole thread Raw
In response to Re: psql and \p\g  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [HACKERS] Re: psql and \p\g  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: psql and \p\g  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
List pgsql-hackers
> On 1999-11-11, Bruce Momjian mentioned:
> 
> > I have found that typing:
> > 
> >     test=> select * from pg_class\p\g
> > 
> > no longer works.  I honors the \p, but ignores the \g.
> > 
> > Any ideas Peter?
> 
> select * from foo \p \g
> 
> This was done to normalize the grammar a little bit (haha, very
> funny). In particular it allows this sort of stuff:
> => select * from foo \p \o out.txt \g \\ select * from foo 2 \x \g
> etc.
> 
> Is it *really* necessary to be able to omit the space?
> 

Yes, I believe it is, in the sense that many people are used to doing
them together.  Can a backslash trigger some separation of commands, or
at least \p\g be recognized correctly.  I don't think there are other
meaningful combinations.

Can you add a unix-style timestamp for \T?

--  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: Bruce Momjian
Date:
Subject: Re: failure of \e in psql
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Slow - grindingly slow - query