> On Nov 7, 2017, at 12:16 AM, Thomas Kellerer wrote:
>
> Rob Sargent schrieb am 06.11.2017 um 23:09:
>> Gosh I wish I could learn to proof-read my posts.
>> My support crew graciously set
>>
>> idle_transaction_timeout = 1
>>
>> Now to ponder if I need zero or some large
On 11/07/2017 09:09 AM, Scott Marlowe wrote:
On Tue, Nov 7, 2017 at 7:44 AM, Rob Sargent wrote:
On Nov 7, 2017, at 12:16 AM, Thomas Kellerer wrote:
I would figure values in "minutes" to be more realistic depending on the
workload and
On Tue, Nov 7, 2017 at 7:44 AM, Rob Sargent wrote:
>
>
>> On Nov 7, 2017, at 12:16 AM, Thomas Kellerer wrote:
>>
>> I would figure values in "minutes" to be more realistic depending on the
>> workload and characteristics of the application.
>>
>> A
> On Nov 7, 2017, at 12:16 AM, Thomas Kellerer wrote:
>
> Rob Sargent schrieb am 06.11.2017 um 23:09:
>> Gosh I wish I could learn to proof-read my posts.
>> My support crew graciously set
>>
>> idle_transaction_timeout = 1
>>
>> Now to ponder if I need zero or some large
Rob Sargent schrieb am 06.11.2017 um 23:09:
> Gosh I wish I could learn to proof-read my posts.
> My support crew graciously set
>
> idle_transaction_timeout = 1
>
> Now to ponder if I need zero or some large number.
The unit of that setting is milliseconds (if no unit is specified).
zero
On 11/06/2017 02:38 PM, Merlin Moncure wrote:
On Mon, Nov 6, 2017 at 2:50 PM, Rob Sargent wrote:
On 11/06/2017 01:41 PM, Tom Lane wrote:
Rob Sargent writes:
idle_in_transaction_session_timeout | 0 | default |
|| A value
On 11/06/2017 02:38 PM, Merlin Moncure wrote:
On Mon, Nov 6, 2017 at 2:50 PM, Rob Sargent wrote:
On 11/06/2017 01:41 PM, Tom Lane wrote:
Rob Sargent writes:
idle_in_transaction_session_timeout | 0 | default |
|| A value
On Mon, Nov 6, 2017 at 2:50 PM, Rob Sargent wrote:
>
>
> On 11/06/2017 01:41 PM, Tom Lane wrote:
>>
>> Rob Sargent writes:
>>>
>>>idle_in_transaction_session_timeout | 0 | default |
>>> || A value of 0 turns off the timeout. |
On 11/06/2017 01:50 PM, Rob Sargent wrote:
On 11/06/2017 01:41 PM, Tom Lane wrote:
Rob Sargent writes:
idle_in_transaction_session_timeout | 0 | default |
|| A value of 0 turns off the timeout. | user
Meh. I think we're barking up the wrong
On 11/06/2017 01:41 PM, Tom Lane wrote:
Rob Sargent writes:
idle_in_transaction_session_timeout | 0 | default |
|| A value of 0 turns off the timeout. | user
Meh. I think we're barking up the wrong tree anyway: so far as I can
find, there is no
Rob Sargent writes:
> idle_in_transaction_session_timeout | 0 | default |
> || A value of 0 turns off the timeout. | user
Meh. I think we're barking up the wrong tree anyway: so far as I can
find, there is no error message reading 'idle
On 11/06/2017 01:17 PM, Tom Lane wrote:
"David G. Johnston" writes:
You should probably login as your application user and do "show
idle_in_transaction_session_timeout" to see what a clean session has for a
value and then figure out from there where that value is
On 11/06/2017 01:09 PM, David G. Johnston wrote:
On Mon, Nov 6, 2017 at 12:32 PM, Rob Sargent >wrote:
Using postgres 10-beta3 (hopefully 10.0 this week) on virtual
CentOS7 and this JDBC driver postgresql:42.1.4
The
"David G. Johnston" writes:
> You should probably login as your application user and do "show
> idle_in_transaction_session_timeout" to see what a clean session has for a
> value and then figure out from there where that value is coming from.
You don't have to guess
On Mon, Nov 6, 2017 at 12:32 PM, Rob Sargent wrote:
> Using postgres 10-beta3 (hopefully 10.0 this week) on virtual CentOS7 and
> this JDBC driver postgresql:42.1.4
>
>
> The postgresql.conf file has
>
> #idle_in_transaction_session_timeout = 0# in milliseconds, 0
Using postgres 10-beta3 (hopefully 10.0 this week) on virtual CentOS7
and this JDBC driver postgresql:42.1.4
The postgresql.conf file has
#idle_in_transaction_session_timeout = 0# in milliseconds, 0
is disabled
my db url has "?prepareThreshold=0" since I bump into "already
16 matches
Mail list logo