Well, you  can try switching to urandom, see
http://stackoverflow.com/questions/137212/how-to-solve-performance-problem-with-java-securerandom,
second answer.

сб, 4 лют. 2017 о 11:45 Vucomir Ianculov <vuko...@os-ux.com> пише:

> Hi Vitalii,
>
> no, hove can i check it? searched but did not find any useful information .
>
> Thanks,
>
> Br,
> Vuko
> ------------------------------
> *From: *"Vitalii Tymchyshyn" <v...@tym.im>
> *To: *"Vucomir Ianculov" <vuko...@os-ux.com>, "Tom Lane" <
> t...@sss.pgh.pa.us>
> *Cc: *pgsql-performance@postgresql.org
> *Sent: *Wednesday, February 1, 2017 7:11:12 PM
>
> *Subject: *Re: [PERFORM] pgsql connection timeone
>
> Just a wild guess, but did you check your random source? We had similar
> problems in Oracle and had to switch to /dev/urandom. It can be done with a
> system variable setting.
>
> On Wed, Feb 1, 2017, 7:52 AM Vucomir Ianculov <vuko...@os-ux.com> wrote:
>
> can anyone help me with my problem?
> i'm really don't know from when the problem can be.
>
>
>
> ------------------------------
> *From: *"Vucomir Ianculov" <vuko...@os-ux.com>
> *To: *"Tom Lane" <t...@sss.pgh.pa.us>
> *Cc: *pgsql-performance@postgresql.org
> *Sent: *Saturday, January 28, 2017 12:03:55 PM
>
> *Subject: *Re: [PERFORM] pgsql connection timeone
>
> Hi Tom,
>
> this is the entry from pg_hba.conf
> host all             all             0.0.0.0/0               md5
>
> i needed to restart postgres service to be able to accept new connection,
> witch it strange becouse there was no load on the server and it head a lot
> of free ram.
>
>
>
>
> ------------------------------
> *From: *"Tom Lane" <t...@sss.pgh.pa.us>
> *To: *"Vucomir Ianculov" <vuko...@os-ux.com>
> *Cc: *pgsql-performance@postgresql.org
> *Sent: *Wednesday, January 25, 2017 3:15:28 PM
> *Subject: *Re: [PERFORM] pgsql connection timeone
>
> Vucomir Ianculov <vuko...@os-ux.com> writes:
> > i'm seeing a lot of connection time out in postgresql log
>
> > 2017-01-25 11:09:47 EET [6897-1] XXX@YYY FATAL: canceling
> authentication due to timeout
> > 2017-01-25 11:10:15 EET [6901-1] XXX@YYY FATAL: canceling
> authentication due to timeout
> > 2017-01-25 11:10:17 EET [6902-1] xxx@YYY FATAL: canceling
> authentication due to timeout
>
> So ... what authentication method are you using?
>
>                         regards, tom lane
>
>

Reply via email to