From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "Josh Kupershmidt" <schmiddy(at)gmail(dot)com> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql setenv command |
Date: | 2011-09-15 23:02:58 |
Message-ID: | 60613.74.9.172.18.1316127778.squirrel@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, September 15, 2011 6:10 pm, Josh Kupershmidt wrote:
> On Thu, Sep 15, 2011 at 10:46 AM, Andrew Dunstan <andrew(at)dunslane(dot)net>
> wrote:
>> this time with patch.
>
> I think help.c should document the \setenv command. And a link from
> the "Environment" section[1] of psql's doc page to the section about
> \setenv might help too.
Good point.
>
> The existing \set command lists all internal variables and their
> values when called with no arguments. Perhaps \setenv with no
> arguments should work similarly: we could display only those
> environment variables interesting to psql if there's too much noise.
> Or at least, I think we need some way to check the values of
> environment variables inside psql, if we're able to set them from
> inside psql. To be fair, I notice that \pset doesn't appear to offer a
> way to show its current values either, but maybe that should be fixed
> separately as well.
\! echo $foo
(which is how I tested the patch, of course)
>
> Typo: s/vakue/value/
>
Yeah, I noticed that after, thanks.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2011-09-16 01:38:55 | Re: Separating bgwriter and checkpointer |
Previous Message | Tom Lane | 2011-09-15 22:53:58 | Re: Initialization of ResultTupleSlot in AppendNode |