From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Robbie Harwood <rharwood(at)redhat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Subject: | Re: [PATCH v6] GSSAPI encryption support |
Date: | 2016-03-14 23:33:33 |
Message-ID: | 56E74A4D.4000502@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/14/16 7:20 PM, Robbie Harwood wrote:
> David Steele <david(at)pgmasters(dot)net> writes:
>
>>
>> Strange timing since I was just testing this. Here's what I got:
>>
>> $ pg/bin/psql -h localhost -U vagrant(at)PGMASTERS(dot)NET postgres
>> conn->inStart = 179, conn->inEnd = 179, conn->inCursor = 179
>> psql (9.6devel)
>> Type "help" for help.
>>
>> postgres=>
>
> Thanks, that certainly is interesting! I did finally manage to
> reproduce the issue on my end, but the rate of incidence is much lower
> than what you and Michael were seeing: I have to run connections in a
> loop for about 10-20 minutes before it makes itself apparent (and no,
> it's not due to entropy). Apparently I just wasn't patient enough.
I'm running client and server on the same VM - perhaps that led to less
latency than your setup?
> All that is to say: thank you very much for investigating that!
My pleasure!
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-03-14 23:52:07 | Re: Explain [Analyze] produces parallel scan for select Into table statements. |
Previous Message | Andres Freund | 2016-03-14 23:28:44 | Re: Timeline following for logical slots |