Re: [phplib] MySQL or PostgreSQL? From: Nuno Silva (nuno_silva <email protected>)
Date: 04/10/01

Hello,

that is true, postgresql don't "overwrite" database data. This is a
design choice, and it let's you do some very cool things like "better
than row locks". This is *very* good for updates and performance.

This makes updates very, very fast (you can even disable fsyncs), but
you should run vacuum nightly. And when you run vacuum you get a sort of
''table global lock'' during the process.

In my experience vaccuming lasts 30secs to 2mins but YMMV.
Having fsyncs disabled makes vacuum run 100 times faster (no joke!)

That said, experimenting is the only way to know for sure.

Regards,
Nuno Silva

Jochen Lillich wrote:

> Hi,
>
> I'm sorry for posting my previous message in German. It's been a long
> day...
>
> I heard that Postgres isn't quite suitable for some web applications,
> because it doesn't do UPDATEs in-place. Instead, it creates new records,
> and the garbage collection with VACUUM would require an exclusive lock.
>
> Is that right -- should I rather use MySQL for storing session data
> and other fast-changing information?
>
> Best regards,
>
> Jochen

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>