| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Gregory Stark <stark(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com> |
| Subject: | Re: FWD: Re: Updated backslash consistency patch |
| Date: | 2009-01-20 15:42:36 |
| Message-ID: | 200901201542.n0KFgaV29667@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Bruce Momjian escribi?:
>
> > In thinking last night, I am now wondering if a letter is really the
> > right symbol for this. We already have letter flags which control
> > object type selection, but the system table addition is kind of
> > independent of those flags, like '+' now. I am thinking maybe '&' is
> > the right symbol rather than 'A' or 'S'.
>
> & is probably going to be useful as a modifier when we have concurrent
> psql, so I suggest you do not use it here. Or maybe not, but in any
> case see
> http://archives.postgresql.org/message-id/8204.1207689056%40sss.pgh.pa.us
> before you use &.
Yea, I thought '&' might be coming for that someday. I figured it
wouldn't be used for backslash commands, but why confuse things.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-01-20 15:44:06 | Re: FWD: Re: Updated backslash consistency patch |
| Previous Message | Bruce Momjian | 2009-01-20 15:41:01 | Re: libpq WSACleanup is not needed |