Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id C22B42E0055 for ; Wed, 4 Jun 2008 14:09:29 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 63936-01 for ; Wed, 4 Jun 2008 14:09:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from tinlc.com (unknown [72.18.206.65]) by developer.postgresql.org (Postfix) with ESMTP id 3C15C2E0054 for ; Wed, 4 Jun 2008 14:09:13 -0300 (ADT) Received: from biglumber.com ([72.18.206.64] helo=localhost) by tinlc.com with smtp (Exim 4.60) (envelope-from ) id 1K3wUl-00038X-0C; Wed, 04 Jun 2008 12:09:55 -0500 From: "Greg Sabino Mullane" To: pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS X-PGP-Key: 2529 DF6A B8F7 9407 E944 45B4 BC9B 9067 1496 4AC8 X-Request-PGP: http://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 In-Reply-To: <72DA5875-8E89-4A6F-8D0B-7F9A869D79B9@kineticode.com> Date: Wed, 4 Jun 2008 17:09:54 -0000 X-Mailer: JoyMail 2.01 Message-ID: <2f7bced0cfe9a1bcc946c7e607528fda@biglumber.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/160 X-Sequence-Number: 119273 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > Exactly. The issue is that application developers, who are not DBAs, > have no idea how to tune PostgreSQL, and postgresql.conf is daunting > and confusing. So they use a different database that's "faster". Changing some of our defaults would go a long way as well. -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkhGzCYACgkQvJuQZxSWSsi2AQCfZFa8PBZ16ljeFNmhY/YlkxF9 8KcAnjciYml1icuuxSPiKIyeE8YrVxOA =q4Cf -----END PGP SIGNATURE-----