From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Craig Boyd <craig(at)mysoftforge(dot)com>, "pgsql-general\(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql connection option: statement_timeout |
Date: | 2016-07-05 19:57:41 |
Message-ID: | 868txfkgcq.fsf@jerry.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Melvin Davidson <melvin6925(at)gmail(dot)com> writes:
> On Sun, Jul 3, 2016 at 7:52 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>
> correction:
>
> alter user reporting set statement_timemout=60 is handy for users that
> should never take a long time to connect.
>
> should read
>
> alter user reporting set statement_timemout=60 is handy for users that
> should never take a long time to run a statement.
>
>>Part of what I am trying to do is understand the delineation between those options I have at connect time as part of the connection string versus those that should be
> scripted...
> Â
> It is fairly simple. The options you have at connect time are documented here:
> https://www.postgresql.org/docs/9.3/static/app-psql.html
>
> All other commands/statements must be executed after connect, specified with the -c option or included in a file with -f .
> Note the exceptions that can be specified per user as Scott mentioned.
No one has mentioned the PGOPTIONS variable here yet ?...
FWIW
> Melvin Davidson
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you. [01]
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Linehan | 2016-07-05 20:17:34 | Re: pg_dump fundenental question |
Previous Message | Sameer Kumar | 2016-07-05 17:54:44 | Re: pg_dump fundenental question |