This is a discussion on Re: setseed accepts bad seeds within the pgsql Bugs forums, part of the PostgreSQL category; --> This has been saved for the 8.4 release: http://momjian.postgresql.org/cgi-bin/pgpatches_hold --------------------------------------------------------------------------- Kris Jurka wrote: > > > On Wed, 11 ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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@momjian.us> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|