Re: setseed accepts bad seeds

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: setseed accepts bad seeds
Date: 2007-04-27 01:07:24
Message-ID: 200704270107.l3R17Om21230@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


This has been saved for the 8.4 release:

http://momjian.postgresql.org/cgi-bin/pgpatches_hold

---------------------------------------------------------------------------

Kris Jurka wrote:
>
>
> 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
Content-Description:

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Dorochevsky,Michel 2007-04-27 07:17:26 Re: BUG #3245: PANIC: failed to re-find shared lock object
Previous Message Tom Lane 2007-04-26 23:31:21 Re: BUG #3245: PANIC: failed to re-find shared lock object