From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a |
Date: | 2009-12-02 21:52:49 |
Message-ID: | 0d4f8d12dd60e921678330562b787950@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> The reason this is a configurable parameter is so that
> people can tune it to their own needs. I think the current
> default fits all right with our usual policy of being
> conservative about hardware requirements.
That only makes sense if you adjust it accordingly over time.
It's been 12 for a long time - since January 2004 - while
hardware has radically improved in that time, which means that
either 12 was too high five years ago, is too low now, or is very
insensitive to the speed of the hardware. I submit it's probably
more of the second option.
The postgresql.conf file has been supporting "a toaster" for a
long time now, but we don't seem to recognize that the minimum
toaster^H^Hhardware encountered in the wild changes quite a
bit from year to year. IMHO.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200912021651
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAksW4YMACgkQvJuQZxSWSsg7gACggzmyKkudzomoleil3PYMnB+z
j+UAoMhi9yEAi8iPBVnailm8jKTe+z39
=++Jr
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2009-12-02 22:08:08 | Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a |
Previous Message | Tom Lane | 2009-12-02 21:11:12 | pgsql: Clarify what's supposed to happen when a cursor FETCH is rolled |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2009-12-02 22:08:08 | Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a |
Previous Message | Tom Lane | 2009-12-02 21:40:05 | Re: Catastrophic changes to PostgreSQL 8.4 |