| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: psql and \p\g |
| Date: | 1999-11-11 21:50:18 |
| Message-ID: | 199911112150.QAA16006@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-11-11 21:51:14 | Re: failure of \e in psql |
| Previous Message | Peter Eisentraut | 1999-11-11 21:37:49 | Re: failure of \e in psql |