Re: Random not so random
От | Harald Fuchs |
---|---|
Тема | Re: Random not so random |
Дата | |
Msg-id | puzn31mj9q.fsf@srv.protecting.net обсуждение исходный текст |
Ответ на | Re: Random not so random ("Arnau Rebassa" <arebassa@hotmail.com>) |
Ответы |
Re: Random not so random
Re: Random not so random |
Список | pgsql-general |
In article <20041004155742.GA8488@wolff.to>, Bruno Wolff III <bruno@wolff.to> writes: > On Mon, Oct 04, 2004 at 10:14:19 -0400, > Tom Lane <tgl@sss.pgh.pa.us> wrote: >> >> It occurs to me that you might be seeing predictability as an indirect >> result of something else you are doing that somehow tends to synchronize >> the backend start times. Are you connecting from a cron script that >> would tend to be launched at the same relative instant within a second? >> >> It might improve matters to make the code do something like >> >> srandom((unsigned int) (now.tv_sec ^ now.tv_usec)); > Using /dev/urandom, where available, might be another option. However, some > people may not want their entropy pool getting 4 bytes used up on every > connection start up. I think we don't need the randomness provided by /dev/[u]random. How about XORing in getpid?
В списке pgsql-general по дате отправления: