| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Arnau Rebassa <arebassa(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Random not so random |
| Date: | 2004-10-04 15:57:42 |
| Message-ID: | 20041004155742.GA8488@wolff.to |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Oct 04, 2004 at 10:14:19 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marco Colombo | 2004-10-04 16:58:41 | Re: Random not so random |
| Previous Message | Scott Marlowe | 2004-10-04 15:25:29 | Re: Server getting crushed |