Peter Eisentraut wrote:
Am Thursday, 17. July 2008 schrieb Bruce Momjian:
Anyways the thing that struck me as odd was the messages appearing
*before* the header. It seems to me the header should print followed by
.psqlrc output followed by normal output.
Do you like this better?
Am Thursday, 17. July 2008 schrieb Bruce Momjian:
Anyways the thing that struck me as odd was the messages appearing
*before* the header. It seems to me the header should print followed by
.psqlrc output followed by normal output.
Do you like this better?
$ psql test
psql
Bruce Momjian wrote:
$ psql test
-- Output format is wrapped.
psql (8.4devel)
Type help for help.
Is this desirable? \set QUIET at the top of .psqlrc fixes it, but I am
wondering if we should be automatically doing quiet while .psqlrc is
processed.
I was
Gregory Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
In my .psqlrc I have:
\pset format wrapped
and this outputs this on psql startup:
$ psql test
-- Output format is wrapped.
psql (8.4devel)
Type help for help.
Is this desirable? \set QUIET at
Neil Conway wrote:
There is some precedent for not emitting the messages: most Unix tools
don't echo the results of applying their .rc files at startup.
Unix shells do echo the output generated by the startup files. It's just that
most Unix tools don't generate that much output.
--
Sent via
Tom Lane wrote:
I think the reason for the current behavior is to allow \set QUIET in
.psqlrc to affect the printing of the banner. Are we prepared to
give that up?
I'm using that behavior!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Wed, 2008-06-11 at 19:24 -0400, Bruce Momjian wrote:
Is this desirable? \set QUIET at the top of .psqlrc fixes it, but I am
wondering if we should be automatically doing quiet while .psqlrc is
processed.
There is some precedent for not emitting the messages: most Unix tools
don't echo the
Neil Conway wrote:
On Wed, 2008-06-11 at 19:24 -0400, Bruce Momjian wrote:
Is this desirable? \set QUIET at the top of .psqlrc fixes it, but I am
wondering if we should be automatically doing quiet while .psqlrc is
processed.
There is some precedent for not emitting the messages: most
In my .psqlrc I have:
\pset format wrapped
and this outputs this on psql startup:
$ psql test
-- Output format is wrapped.
psql (8.4devel)
Type help for help.
Is this desirable? \set QUIET at the top of .psqlrc fixes it, but I am
wondering if we should be
Bruce Momjian [EMAIL PROTECTED] writes:
In my .psqlrc I have:
\pset format wrapped
and this outputs this on psql startup:
$ psql test
-- Output format is wrapped.
psql (8.4devel)
Type help for help.
Is this desirable? \set QUIET at the top of .psqlrc fixes
Gregory Stark [EMAIL PROTECTED] writes:
Anyways the thing that struck me as odd was the messages appearing *before*
the header. It seems to me the header should print followed by .psqlrc output
followed by normal output.
I think the reason for the current behavior is to allow \set QUIET in
11 matches
Mail list logo
