On Tue, Nov 08, 2011 at 06:36:52AM +0200, Peter Eisentraut wrote:
> Here is an updated patch that addresses all the issues you pointed out.
Looks ready to me. Thanks.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresq
On lör, 2011-11-05 at 12:26 -0400, Noah Misch wrote:
> On Sat, Nov 05, 2011 at 04:53:56PM +0200, Peter Eisentraut wrote:
> > On fre, 2011-11-04 at 07:34 -0400, Noah Misch wrote:
> > > For "\pset format wrapped", we only use $COLUMNS when the output is a
> > > tty. I'm thinking it's best, although
On Sat, Nov 05, 2011 at 04:53:56PM +0200, Peter Eisentraut wrote:
> On fre, 2011-11-04 at 07:34 -0400, Noah Misch wrote:
> > For "\pset format wrapped", we only use $COLUMNS when the output is a
> > tty. I'm thinking it's best, although not terribly important, to
> > apply the same rule to this fe
On fre, 2011-11-04 at 07:34 -0400, Noah Misch wrote:
> For "\pset format wrapped", we only use $COLUMNS when the output is a
> tty. I'm thinking it's best, although not terribly important, to
> apply the same rule to this feature.
I think it does work that way. There is only one place where the
On 17 December 2010 22:12, Peter Eisentraut wrote:
> I have often found myself wanting that psql automatically switch between
> normal and \x mode depending on the width of the output. Would others
> find this useful?
+1
Sounds like a very good idea.
--
Peter Geoghegan http://www.2ndQu
On Tue, Nov 01, 2011 at 06:22:47AM +0200, Peter Eisentraut wrote:
> I wrote:
> > I have often found myself wanting that psql automatically switch between
> > normal and \x mode depending on the width of the output. Would others
> > find this useful?
> >
> > Attached is a crude demo patch. Enable
Peter Eisentraut writes:
> Here is a finalized patch for this. The first hunk of the patch is the
> documentation change, so you can see there how it's supposed to work.
> Let me know what you think.
+1
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et
I have not tried the patch (yet), but Informix'sl dbacess would do about
the same - and it's something I really missed.
Jan
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to y
I wrote:
> I have often found myself wanting that psql automatically switch between
> normal and \x mode depending on the width of the output. Would others
> find this useful?
>
> Attached is a crude demo patch. Enable with \pset expanded auto.
Here is a finalized patch for this. The first hun
I have added a link to this on the TODO list:
Add "auto" expanded mode that outputs in expanded format if "wrapped"
mode can't wrap the output to the screen width
* Re: psql wrapped format default for backslash-d commands
* http://archives.postgres
Peter Eisentraut wrote:
> I have often found myself wanting that psql automatically switch between
> normal and \x mode depending on the width of the output. Would others
> find this useful?
>
> Attached is a crude demo patch. Enable with \pset expanded auto.
It is a TODO:
Add auto-exp
On Sat, Dec 18, 2010 at 07:12, Peter Eisentraut wrote:
> I have often found myself wanting that psql automatically switch between
> normal and \x mode depending on the width of the output. Would others
> find this useful?
+1
> Attached is a crude demo patch. Enable with \pset expanded auto.
H
pete...@gmx.net (Peter Eisentraut) writes:
> I have often found myself wanting that psql automatically switch between
> normal and \x mode depending on the width of the output. Would others
> find this useful?
I haven't tested the patch, but that *does* sound generally useful.
It's no fun trying
13 matches
Mail list logo
