Re: Postgres v MySQL 5.0 - Mailing list pgsql-advocacy

> > A smart developer, will review his options. A smart developer knows
> > there is more to it than just plugging it in and watching the flashing
> > lights. There are times when MySQL *is* faster and more approporiate to
> > use than PostgreSQL and vice versa.. but the plug-n-play argument is
> > false.
> >
> > It reminds me of the conversation I had with a java developer on
> > #postgresql . They guy logs on and says,
> >
> > Dev: PostgreSQL is slow
> > Me: What seems to be the problem
> > Dev: I am using Hibernate and my queries are slow
> > Me: Do you vacuum? Did you analyze? What does the explain say?
> > Dev: parse error
> > Me: ??maintenance
> > Dev: You mean there is stuff you have to do to the database beside
> > Hibernate config?
> > Me: /quit
>
> Well I think you fail to understand here that a developer != DBA. So a
> developer without a DBA is smart if he chooses an RDBMS that requires
> little manual maintenance.

No, I understand it perfectly and I stand by my assertion. That
developer, should have either:

A. Worked with a DBA
B. Learned to be a DBA
C. Spent one day just getting the at least the basics down

If he is too lazy or dumb to do that, I don't want him near my
application and I do feel sorry the person that hired him. The person
that hired him is going to spend a great deal more fixing all of the
mistakes he makes because he didn't do his homework than he would of if
he actually paid a professional.

A professional would not take the same approach as the developer you
mention or the developer I spoke with. A professional does what needs to
be done to make sure that the application is done right.

> have invested this initial time, you are more likely to spend the
> additional time/money to tweaks things once you hit a wall. But at that
> point you can actually afford to do so!
>

Can you?

/me points at drupal
/me points at slashdot
/me points at (a bunch of customers I have that have spent entirely too
much money fixing mysql problems by porting to postgresql than they
would have if they just did it right the first time)

Sincerely,

Joshua D. Drake


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate