Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] Bug #718: request for improvement of /? to show

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ian Barwick <barwick(at)gmx(dot)net>, Harald Armin Massa <ghum(at)gmx(dot)net>,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [BUGS] Bug #718: request for improvement of /? to show
Date: 2002-12-11 23:08:23
Message-ID: 200212112308.gBBN8NR05589@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > OK, new output attached.  Does the HTML section look silly now with only
> > two entries?
> 
> Yeah.  I think it should be folded into "Formatting", since it really is
> only an output-formatting option.
> 
> I have a problem with the "Query Buffer" section, also: I don't think
> \i, \o, etc have anything to do with the query buffer.  Could we split
> this section into "Query Buffer" (\g \r \e \p \w) and "I/O Redirection"
> (\i \o \s), or something like that?  Perhaps \copy could go into the
> redirection section too, rather than suffering a shotgun wedding with
> the large-object commands.

OK, I have created an "I/O  Redirection" section and moved \i and \o
into there.  I didn't think \s (history) belonged there.  I also
couldn't see \copy as I/O redirection.  (It is a shotgun wedding,
though.)

I have moved Formatting above the "shotgun wedding."

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

Responses

pgsql-patches by date

Next:From: Bruce MomjianDate: 2002-12-11 23:08:46
Subject: Re: [BUGS] Bug #718: request for improvement of /? to show
Previous:From: Bruce MomjianDate: 2002-12-11 22:45:47
Subject: Re: [BUGS] Bug #718: request for improvement of /? to show

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group