public inbox for [email protected]
help / color / mirror / Atom feedFrom: Shridhar Daithankar <[email protected]>
To: [email protected]
Subject: Re: PostgreSQL vs. MySQL
Date: Fri, 4 Jul 2003 20:58:12 +0530
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
On Friday 04 July 2003 20:56, Andrew Sullivan wrote:
> On Fri, Jul 04, 2003 at 04:35:03PM +0200, Michael Mattox wrote:
> > I see this as a major problem. How many people run postgres, decide it's
> > too slow and give up without digging into the documentation or coming to
> > this group? This seems to be pretty common. Even worst, they tell 10
> > others how slow Postgres is and then it gets a bad reputation.
>
> There have been various proposals to do things of this sort. But
> there are always problems with it. For instance, on many OSes,
> Postgres would not run _at all_ when you first compiled it if its
> defaults were set more agressively. Then how many people would
> complain, "It just doesn't work," and move on without asking about
> it?
There was a proposal to ship various postgresql.conf.sample like one for large
servers, one for medium, one for update intensive purpose etc.
I was thinking over it. Actaully we could tweak initdb script to be
interactiev and get inputs from users and tune it accordingly. Of course it
would be nowhere near the admin reading the docs. but at least it won't fall
flat on performance groundas the way falls now.
Shridhar
view thread (66+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: PostgreSQL vs. MySQL
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox