From: | "Gordan Bobic" <gordan(at)freeuk(dot)com> |
---|---|
To: | "MYSQL" <mysql(at)lists(dot)mysql(dot)com>, "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: SV: MySQL and PostgreSQL speed compare |
Date: | 2001-01-02 10:01:58 |
Message-ID: | 004b01c074a3$1fdc5ac0$8000000a@localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
[tuning analogies snipped]
>
> Likewise with self-proclaimed computer tuners.
You have no idea how much I agree with you there.
> > I really don't understand why people expect computers to do everything
> > for them, the burden of using tools properly belongs to the user.
>
> I of course agree in principle to this statement (and the whole tone of
> your reply) -- but, my statement doesn't reflect my opinion -- it
> reflects reality. Facts are stubborn things.
>
> Of course the defaults will never be perfect -- nor will all users RTM.
> But, therein lies the utility of 'defaults' benchmarking -- let's see
> what the trade offs really are so that we the 'experts' can
> intelligently recommend things -- as well as intelligently tweak the
> defaults.
Unfortunately, there are two ways you can load the defaults. You can strip
them down for maximum speed, or you can load them up for maximum
reliability. The latter will make the users complain about speed on the
support lists in a generally annoyed fashion.
Stripping things down for sppeed, OTOH, will work great - until someone
gets a powercut, or some other kind of wierd hardware failure that will
wipe out their data. Then they will come back again and complain.
And the answer is always to simply spend an hour or so reading the
documentation...
Some people, eh...
Regards.
Gordan
From | Date | Subject | |
---|---|---|---|
Next Message | Gordan Bobic | 2001-01-02 10:05:13 | Re: How passwords can be crypted in postgres? |
Previous Message | Michael Davis | 2001-01-02 09:46:27 | pg_dump/psql < db.out issue |