Re: [phplib] MySQL or PostgreSQL? From: fabrizio.ermini <email protected>
Date: 04/11/01

On 10 Apr 2001, at 19:01, Jochen Lillich wrote:
> I'm sorry for posting my previous message in German. It's been a long
> day...
>
Don't worry, we won't take that an offense. Besides, AFAIK there
are many german speaking people around here...

> 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?
>

First assumption is right, second not. Actually, postgres has a
much more efficient locking policy so it's a lot faster for apps that
have frequent updates. The drawback it's the vacuum thingy;
however, almost all sites can do it during low-traffic hours (you can
also vacuum each table separately, to "distribute" the load) without
serious consequences.

Instead, I will suggest MySQL for read-intensive apps, since its
speed can't be beaten for that (at least as long as concurrent
connections do not grow too many).

BTW, they say that using PHP4 native sessions support it's
always better than using a DB as a container. Just for
completeness...

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

Fabrizio Ermini Alternate E-mail:
C.so Umberto, 7 faermini <email protected>
loc. Meleto Valdarno Mail on GSM: (keep it short!)
52020 Cavriglia (AR) faermini <email protected>

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