From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "PostgreSQL advocacy" <pgsql-advocacy(at)postgresql(dot)org> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: What can we learn from MySQL? |
Date: | 2004-04-23 12:27:11 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB34101ADCD@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Bruce Momjian wrote:
> My question is, "What can we learn from MySQL?" I don't know there is
> anything, but I think it makes sense to ask the question.
Here is one thing I can suggest from personal experience. PostgreSQL is
easy to configure and install; one of the easiest out there. That's
mostly moot anyways since most of the popular distros come with pg
pre-installed (although you still have to know how to upgrade it).
Recompiling php and apache (and hooking everything up together),
however, is not always so easy. I think lobbying the php/distros to
have postgres support compiled into php in the default installation
would be a big help from adoption. mysql's grass roots support comes
from free tools like phpnuke and others.
One thing that could use a little work in the manual is practial issues
when dealing with application development...especially transactions,
locking, and concurrency issues which tend to come up in applications.
Why/When to use them, benefits, gotchas, etc. etc. Think 'best
practices' or strategies. There is an excellent tutorial in the docs
wrt the rule system,..there could be more stuff like that.
Oh, a couple of days ago someone mentioned a wiki...that would be great.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | David Costa | 2004-04-23 12:32:50 | Re: What can we learn from MySQL? |
Previous Message | Tom Lane | 2004-04-23 11:45:54 | Re: [HACKERS] What can we learn from MySQL? |