| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: setseed accepts bad seeds |
| Date: | 2007-04-11 18:51:09 |
| Message-ID: | Pine.BSO.4.64.0704111449410.20552@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 11 Apr 2007, Tom Lane wrote:
> 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.
>
Then please consider this patch which checks the range and maps the
provided value to the entire seed space.
Kris Jurka
| Attachment | Content-Type | Size |
|---|---|---|
| setseed.patch | text/plain | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Darville | 2007-04-12 12:19:48 | Continuous archiving fails |
| Previous Message | Tom Lane | 2007-04-11 18:29:35 | Re: setseed accepts bad seeds |