Re: Raising the geqo_threshold default - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Raising the geqo_threshold default
Date
Msg-id 892cef254a8267dc7d226a6c59ec376c@biglumber.com
Whole thread Raw
In response to Re: Raising the geqo_threshold default  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Raising the geqo_threshold default
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----                            
Hash: RIPEMD160                                               


Tom Lane replied:
>> Is there any chance we can raise the default geqo_threshold from
>> its current default of 12?

> We were over that just a few months ago.

Tom, that was a very unhelpful reply. I don't have the luxury of
reading, much less remembering, every thread that has occurred on
the hackers mailing list. Perhaps you mean the discussion from
July 6, 2009 started by Robert Haas? That was approximately 8000
messages ago, and no consensus was reached that I could find. So
I'd like to respectfully ask the hackers to consider raising the
default value from 12 to 16 (as Robert Haas first suggested) or
even higher (20?). Whether or not we make GEQO less random, replace
it someday with something else, tweak *_collapse_limit, etc. is not
as important in my mind as minimizing this unexpected foot gun for
future releases. Thanks.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200911170859
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAksCrIIACgkQvJuQZxSWSsjReACgihBX9gD+VE6kcd5gsFPjtigj
xgEAoM4S4tRj/PsMEVUEM5K6taGGUWfm
=2WB4
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: Rejecting weak passwords
Next
From: Andrew Dunstan
Date:
Subject: Re: UTF8 with BOM support in psql