Tom Lane wrote:
> Bruce Momjian writes:
> > Dennis Bjorklund wrote:
> >> My motivation is only for the good of postgresql. If the majority want
> >> something else then that's what should happen (of course). I'm just
> >> stating my view, nothing less and nothing more.
>
> > I am surprised we ha
Bruce Momjian writes:
> Dennis Bjorklund wrote:
>> My motivation is only for the good of postgresql. If the majority want
>> something else then that's what should happen (of course). I'm just
>> stating my view, nothing less and nothing more.
> I am surprised we have not gotten more comments ab
Dennis Bjorklund wrote:
> My motivation is only for the good of postgresql. If the majority want
> something else then that's what should happen (of course). I'm just
> stating my view, nothing less and nothing more.
I am surprised we have not gotten more comments about it. I personally
like the
On Sat, 26 Nov 2005, Bruce Momjian wrote:
> See the discussion or really solo request by me for more feedback when
> this change was made for 8.1:
>
> http://archives.postgresql.org/pgsql-patches/2005-06/msg00295.php
>
> Where were you when I asked?
I do not work with postgresql like you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Well, that's hardly a reason to add something to the client that is
> already in the backend. A much more general solution would be to either
> add a flag to SHOW ALL to supress the extra column (or one to add it),
An even more general solution i
Dennis Bjorklund wrote:
> On Fri, 25 Nov 2005, Bruce Momjian wrote:
>
> > > > Is there any use for SHOW except in interactive psql sessions?
> >
> > There certainly is. Imagine querying for timezone. Also remember that
> > pgadmin is a client application that is _not_ psql.
>
> I should have w
On Fri, Nov 25, 2005 at 08:25:55PM -0300, Alvaro Herrera wrote:
> (I just noticed that Martijn's patch is not about auto-wrapping but
> about displaying \n correctly, which is quite different. So while there
> may be some common code it certainly is not the same thing.)
Auto-wrapping has been con
On Fri, 25 Nov 2005, Bruce Momjian wrote:
> > > Is there any use for SHOW except in interactive psql sessions?
>
> There certainly is. Imagine querying for timezone. Also remember that
> pgadmin is a client application that is _not_ psql.
I should have written SHOW ALL, that's the command outp
Alvaro Herrera wrote:
> Dennis Bjorklund wrote:
>
> > My main problem with SHOW as it is in 8.1 is that the output is so wide
> > that it's very hard to read the output.
> >
> > Is there any use for SHOW except in interactive psql sessions?
There certainly is. Imagine querying for timezone. A
Alvaro Herrera wrote:
> > > I think a \show would be nice, but deprecating SHOW is out of the
> > > question. (The pg_settings view is a perfect replacement AFAICS but I
> > > doubt we can get rid of the old interface.)
> > >
> > > OTOH, what's the relationship between \show and Martijn's wide ou
Dennis Bjorklund wrote:
> My main problem with SHOW as it is in 8.1 is that the output is so wide
> that it's very hard to read the output.
>
> Is there any use for SHOW except in interactive psql sessions?
Nothing that can't be done by querying pg_settings.
--
Alvaro Herrera
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Dennis Bjorklund wrote:
> >
> > > > Actually, I'm going to implement a \show command and send to -patches
> > > > and
> > > > then SHOW can even be deprecated (if we want). SHOW is just a command
> > > > line
> > > > cli
On Fri, 25 Nov 2005, Bruce Momjian wrote:
> > OTOH, what's the relationship between \show and Martijn's wide output
> > patch? Maybe the problem can be solved in a different way.
>
> What does \show do that SHOW does not?
It could do several things. For example \show could omit the description
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Dennis Bjorklund wrote:
>
> > > Actually, I'm going to implement a \show command and send to -patches and
> > > then SHOW can even be deprecated (if we want). SHOW is just a command line
> > > client command, that is implemented in the server. That
On Fri, Nov 25, 2005 at 07:24:13PM -0300, Alvaro Herrera wrote:
> OTOH, what's the relationship between \show and Martijn's wide output
> patch? Maybe the problem can be solved in a different way.
None whatsoever. OTOH, there has been discussion about making use of
multiline output if it can be d
Bruce Momjian wrote:
> Dennis Bjorklund wrote:
> > Actually, I'm going to implement a \show command and send to -patches and
> > then SHOW can even be deprecated (if we want). SHOW is just a command line
> > client command, that is implemented in the server. That is not how we
> > normally do thin
Dennis Bjorklund wrote:
> I've noticed that in 8.1 the output of SHOW ALL includes a description
> column. This makes the output very wide which makes it hard to use from
> psql (I need to make the terminal window 164 characters wide to not get
> any line wrapping). I wish I would have noticed this
I've noticed that in 8.1 the output of SHOW ALL includes a description
column. This makes the output very wide which makes it hard to use from
psql (I need to make the terminal window 164 characters wide to not get
any line wrapping). I wish I would have noticed this before 8.0 was out
and then I
18 matches
Mail list logo
