| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net> |
| Cc: | "Marko Kreen" <markokr(at)gmail(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: The Axe list |
| Date: | 2008-10-12 15:58:23 |
| Message-ID: | 9358.1223827103@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"D'Arcy J.M. Cain" <darcy(at)druid(dot)net> writes:
> On Sun, 12 Oct 2008 12:57:58 +0300
> "Marko Kreen" <markokr(at)gmail(dot)com> wrote:
>> This is bad idea, postgres already does srandom()
> Is that new? I added that to my local version at one time because I
> was getting the same salt every time I ran it.
Quite a while ago we went around and removed random calls to srandom.
In any case it is *not* acceptable to put one into a datatype, because
the effects are global. If we did have a problem like that, the
appropriate solution would be elsewhere.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-10-12 16:36:38 | Re: The Axe list |
| Previous Message | Hitoshi Harada | 2008-10-12 15:22:33 | Re: SELECT TOP %d PERCENT, or SELECT ... LIMIT %d PERCENT ? |