Re: [BUGS] Bug #718: request for improvement of /? to show - Mailing list pgsql-patches

From Tom Lane
Subject Re: [BUGS] Bug #718: request for improvement of /? to show
Date
Msg-id 8797.1039580825@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] Bug #718: request for improvement of /? to show  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [BUGS] Bug #718: request for improvement of /? to show  ("Ross J. Reedstrom" <reedstrm@rice.edu>)
Re: [BUGS] Bug #718: request for improvement of /? to show  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [BUGS] Bug #718: request for improvement of /? to show  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.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.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [BUGS] Bug #718: request for improvement of /? to show /d+ /l+
Next
From: "Christoph Zwerschke"
Date:
Subject: Re: PyGreSQL, suggestion for DB wrapper class