| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: setseed accepts bad seeds |
| Date: | 2007-04-11 18:29:35 |
| Message-ID: | 29854.1176316175@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Kris Jurka <books(at)ejurka(dot)com> writes:
> On Wed, 11 Apr 2007, Tom Lane wrote:
>> Kris Jurka <books(at)ejurka(dot)com> writes:
>>> Why doesn't setseed complain when given a seed value outside of its
>>> expected range?
>>
>> Why should it complain? The use of the value is totally unspecified
>> anyway.
> Because the user is likely using it incorrectly.
It's not really possible to use it "incorrectly", AFAICS. Any value you
might pass to it will result in a specific new seed value. Nowhere is
there any guarantee of what the mapping is, and it's obviously
impossible to guarantee that the mapping is one-to-one, so any user
assumptions about what a specific seed value might "mean" seem broken
regardless.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2007-04-11 18:51:09 | Re: setseed accepts bad seeds |
| Previous Message | Kris Jurka | 2007-04-11 17:37:35 | Re: setseed accepts bad seeds |