Do we have any way of seeing all the predefined psql \set setting?
Right now if you do \set, you see the settings for that client, but you
don't see a list of setting the psql understands, like autocommit. You
can only see those in the psql manual.
On the server side, we have SHOW ALL which sh
> This is irrelevant to what I'm doing, in any case, and it's not an itch
> I feel personally. Work on it yourself if you want it ...
OK, I figured it out. :-)
It's a fairly short patch in 7.3.3, what do I need to do to submit it
for 7.4?
I also made a minor functional change that may need to
--On Wednesday, June 25, 2003 22:58:39 -0400 Tom Lane <[EMAIL PROTECTED]>
wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
One way I could imagine doing it is to split log_min_messages into
three variables, along the lines of "minimum message level to produce
a TERSE report", "m
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> One way I could imagine doing it is to split log_min_messages into
>> three variables, along the lines of "minimum message level to produce
>> a TERSE report", "minimum message level to produce a DEFAULT report",
>> and "minimum message
Tom Lane wrote:
> Kevin Brown <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Also, I would like to provide the same set of options w.r.t. messages
> >> logged in the server log. Here there is an additional frammish that
> >> could be imagined, ie, more detail for more-serious errors. Any
>
Kevin Brown <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Also, I would like to provide the same set of options w.r.t. messages
>> logged in the server log. Here there is an additional frammish that
>> could be imagined, ie, more detail for more-serious errors. Any
>> opinions about what it sh
[EMAIL PROTECTED] wrote:
> > [EMAIL PROTECTED] writes:
> > > Is it too late to suggest that there be a way to have output displayed
> > > on screen AND output to a file?
> >
> > tee perhaps?
>
> Tee ALMOST does it. Try doing a \d while tee'ing the output, for example.
Try using "script" (star
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I think 'is_superuser' is more appropriate.
>
> Okay, fine.
>
> I forgot one other thing that is available from the recent libpq
> additions and needs to be exposed by psql: error message verbosity
> setting.
>
> What's there now is
Arguile <[EMAIL PROTECTED]> writes:
> On Wed, 2003-06-25 at 13:49, Tom Lane wrote:
>> The first choice seems less verbose to me, but if anyone wants to make a
>> case for the second, I'm open to it. Note that either of these could be
>> put in ~/.psqlrc if someone wants autocommit off as their def
> [EMAIL PROTECTED] writes:
> > Is it too late to suggest that there be a way to have output displayed
> > on screen AND output to a file?
>
> tee perhaps?
Tee ALMOST does it. Try doing a \d while tee'ing the output, for example.
I don't quite get everything back before it asks for the next i
On Wed, 2003-06-25 at 13:49, Tom Lane wrote:
> There are a number of things that need to be done in psql before feature
> freeze. Any comments on the following points?
>
> * We need a client-side autocommit-off implementation to substitute for
> the one removed from the server. I am inclined to
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I think 'is_superuser' is more appropriate.
Okay, fine.
I forgot one other thing that is available from the recent libpq
additions and needs to be exposed by psql: error message verbosity
setting.
What's there now is described in
http://candle.pha.pa.u
[EMAIL PROTECTED] writes:
> Is it too late to suggest that there be a way to have output displayed
> on screen AND output to a file?
tee perhaps?
This is irrelevant to what I'm doing, in any case, and it's not an itch
I feel personally. Work on it yourself if you want it ...
Is it too late to suggest that there be a way to have output displayed
on screen AND output to a file?
I've got my Oracle systems set up so that all sqlplus sessions do this,
complete with using the process or session number as part of the output
file name so each is unique.
This gives me a r
From: "Tom Lane" <[EMAIL PROTECTED]>
> It would be easy (and essentially free, since libpq already gets the info)
> to add such a notice to psql startup. How do other people feel about
> it? How would you word the notice exactly?
> "psql: server version is FOO, psql version is BAR, some things ma
[EMAIL PROTECTED] writes:
>> Not sure how important that really is, given that we don't recommend
>> running psql against servers of different versions.
> We also do not check the version or throw a warning on a mismatched
> version, something I think it may be time to reevaluate.
It would be e
Tom Lane wrote:
> There are a number of things that need to be done in psql before feature
> freeze. Any comments on the following points?
>
> * We need a client-side autocommit-off implementation to substitute for
> the one removed from the server. I am inclined to create a new psql
> backslash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Since libpq now keeps track of transaction state, it would be a simple
> matter to add a prompt-string % construct to show something that indicates
> the state
greg=> SELECT 'I am idle';
greg=*> SELECT 'I am in a transaction';
greg=!> SELECT 'I
18 matches
Mail list logo
