Re: [GENERAL] psql connection option: statement_timeout

2016-07-05 Thread Jerry Sievers
Melvin Davidson writes: > On Sun, Jul 3, 2016 at 7:52 PM, Scott Marlowe 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 state

Re: [GENERAL] psql connection option: statement_timeout

2016-07-04 Thread Craig Boyd
On 07/04/2016 11:01 AM, Daniel Verite wrote: Craig Boyd wrote: So to put it another way: is there a list that shows what options are available during the connection event or as part of the connection string? Yes, but it belongs to the chapter on libpq. The psql docpage merely points to

Re: [GENERAL] psql connection option: statement_timeout

2016-07-04 Thread Daniel Verite
Craig Boyd wrote: > So to put it another way: is there a list that shows what options are > available during the connection event or as part of the connection string? Yes, but it belongs to the chapter on libpq. The psql docpage merely points to it: -d dbname --dbname=dbname

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Craig Boyd
On 07/03/2016 07:00 PM, Melvin Davidson wrote: On Sun, Jul 3, 2016 at 7:52 PM, Scott Marlowe > wrote: correction: alter user reporting set statement_timemout=60 is handy for users that should never take a long time to connect. should read

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Craig Boyd
On 07/03/2016 06:51 PM, Scott Marlowe wrote: On Sun, Jul 3, 2016 at 5:15 PM, Melvin Davidson > wrote: On Sun, Jul 3, 2016 at 6:54 PM, Craig Boyd mailto:cr...@mysoftforge.com>> wrote: Hello All, I am something of a newbie and I am trying to und

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Melvin Davidson
On Sun, Jul 3, 2016 at 7:52 PM, Scott Marlowe 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

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Scott Marlowe
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. -- Sent via pgsql-general mailing l

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Scott Marlowe
On Sun, Jul 3, 2016 at 5:15 PM, Melvin Davidson wrote: > > > On Sun, Jul 3, 2016 at 6:54 PM, Craig Boyd wrote: > >> Hello All, >> >> I am something of a newbie and I am trying to understand how to pass >> connection options using the psql client. My understanding is that it is >> possible to do

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Craig Boyd
On 07/03/2016 06:15 PM, Melvin Davidson wrote: On Sun, Jul 3, 2016 at 6:54 PM, Craig Boyd > wrote: Hello All, I am something of a newbie and I am trying to understand how to pass connection options using the psql client. My understanding is tha

Re: [GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Melvin Davidson
On Sun, Jul 3, 2016 at 6:54 PM, Craig Boyd wrote: > Hello All, > > I am something of a newbie and I am trying to understand how to pass > connection options using the psql client. My understanding is that it is > possible to do this as part of the psql connection event. > I am on Mint and my Pos

[GENERAL] psql connection option: statement_timeout

2016-07-03 Thread Craig Boyd
Hello All, I am something of a newbie and I am trying to understand how to pass connection options using the psql client. My understanding is that it is possible to do this as part of the psql connection event. I am on Mint and my PostgreSQL Server version = 9.3.13. I am trying to connect to