On Sat, May 24, 2008 at 11:57 AM, Ram Ravichandran <[EMAIL PROTECTED]> wrote:
> ..."High Performance MySQL" ...
BTW: The current version of this book is (somewhat) out of date, and
the next version will be released in next few months.
--
Rob Wultsch
[EMAIL PROTECTED]
--
Sent via pgsql-general m
Steve Atkins wrote:
Hang out on the pgsql-performance mailing list and see what other people
do - "How do I tune a database for X" comes up pretty regularly, and
gets good answers, so trolling through the mailing list archive can give
some very good advice.
Aside from the hardware and serv
On 5/24/08, Ram Ravichandran <[EMAIL PROTECTED]> wrote:
> I am deciding between MySQL and Postgres. I'm leaning towards Postgres
> mainly due the widely publicized speed when using transactions. However, I
> am not able to find any good books / resources for tuning/ optimizing the
> database. Is th
On May 24, 2008, at 11:57 AM, Ram Ravichandran wrote:
Hi,
I am deciding between MySQL and Postgres. I'm leaning towards
Postgres mainly due the widely publicized speed when using
transactions. However, I am not able to find any good books /
resources for tuning/ optimizing the database.
Ram Ravichandran wrote:
Hi,
I am deciding between MySQL and Postgres. I'm leaning towards Postgres
mainly due the widely publicized speed when using transactions.
Everything except for a couple of actions in Postgresql are wrapped in
transactions and can be rollback, you can not turn it off
