Raising the geqo_threshold default - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Raising the geqo_threshold default
Date
Msg-id 7a2dd95083af1c9d42e839828af94243@biglumber.com
Whole thread Raw
Responses Re: Raising the geqo_threshold default
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Is there any chance we can raise the default geqo_threshold from
its current default of 12? This seems too low, as a modern Postgres
on modern hardware has no problem with 12 table joins. However, I have
seen geqo causing trouble for clients when they hit 12 and get
random (and crappy) query plans. Is the value of 12 based on any
recent measurements? Thanks.

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

iEYEAREDAAYFAksCCN8ACgkQvJuQZxSWSsihOwCgyRldD/QS63rQzcBO6ZoyI/zH
NPUAoNmkgf3Txr/V6p2oZJ/tNY8gx/mt
=u1ut
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: next CommitFest
Next
From: Greg Smith
Date:
Subject: Re: Partitioning option for COPY