This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> Hi,
>
> I basically have a functional version for al
On Tue, Sep 27, 2005 at 12:12:15AM -, Greg Sabino Mullane wrote:
> > 4. Some system output like pg_views has really really long strings,
> > would it be acceptable to change the output there to add newlines at
> > various places to make it output nicer with this change?
>
> I'd say no, until y
On Tue, Sep 27, 2005 at 03:02:29PM +0200, Peter Eisentraut wrote:
> I don't think this is necessary. If you put control characters into your
> text, then you clearly don't care about aligned output, so you don't get any.
>
> About \r, I think that needs to be figured into the alignment calcula
Am Sonntag, 25. September 2005 22:45 schrieb Martijn van Oosterhout:
> 1. To be able to control the spacing, psql now has to be very careful
> about its output. eg \r is printed as \r, ascii control characters are
> output as \x00 style and other control chars as \u. This is a
> change from pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> 3. How to show that a value is continued? As you can see below I use
>...
> I remember a discussion on this before but couldn't find it in the
> archives. Either a reference or some other hints would be appreciated.
I think we liked the "+" charac
Hi,
I basically have a functional version for aligned output, examples at
the bottom of this email. It handles multiline data values and
multiline headers. However, there are some areas where I could use some
input.
1. To be able to control the spacing, psql now has to be very careful
about its o
