From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql setenv command |
Date: | 2011-11-02 21:36:24 |
Message-ID: | 4EB1B7D8.2080002@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/26/2011 05:16 PM, Andrew Dunstan wrote:
>
>
> On 09/26/2011 05:07 PM, Jeff Janes wrote:
>>
>> But in any case, considering that we are both wondering if it works on
>> Windows, I think that argues that an automatic regression test would
>> be very handy.
>>
>>
>
> I think an automated test should be possible. Something like:
>
> \setenv PGFOO blurfl
> \! echo $PGFOO %PGFOO%
>
>
> and then have a couple of alternative results. When I get time to get
> back to this I'll experiment.
>
>
I can confirm it does work on Windows:
C:\prog\bf\root\HEAD\testinst>type ..\..\..\setenv.sql
\setenv PGFOO foo
\! echo $PGFOO %PGFOO%
\setenv PGFOO
\! echo $PGFOO %PGFOO%
C:\prog\bf\root\HEAD\testinst>bin\psql -f ..\..\..\setenv.sql postgres
$PGFOO foo
$PGFOO %PGFOO%
I think I agree on reflection with Josh Kupershmidt that we don't need a
regression test for this.
Updated patch is attached - adding to Nov commitfest.
cheers
andrew
Attachment | Content-Type | Size |
---|---|---|
setenv.patch | text/x-patch | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2011-11-02 22:02:39 | Re: pg_dump --exclude-table-data |
Previous Message | Heikki Linnakangas | 2011-11-02 21:01:26 | Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) |