Melvin Davidson <melvin6925@gmail.com> writes:
> On Sun, Jul 3, 2016 at 7:52 PM, Scott Marlowe <scott.marlowe@gmail.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
theconnection 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.consulting@comcast.net
p: 312.241.7800