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

Matthias Mohr wrote:

[snip...]

>
> I agree 100%. And I don't know what are the drawbacks of such an exclusive
> lock. postgres ist quite aware of concurrend access, and vacuum is just one of
> them. i just ran
>
> #!/usr/bin/tcsh
> while ( 1 )
> echo "vacuum;"|psql messju
> end
>
> and i did not mention any problems to connect and query the database while
> running the "endless vacuum". of course the second to nth vacuum is done very
> fast and this is not a representive environment, but when it comes to
> concurrend (the one you mentionend is "vacuum" against access from the
> weberver), i cannot imagine anything that makes mysql superior to postgres.

in a *very* busy environment (with lots of updates) the first vacuum can
take some time because of the garbage collection stuff... after that the
vacuum does pretty much nothing :)

anyway, I think that the advantages of "better than row level locking"
in postgres makes this vacuum a tiny price to pay :)
...not to mention subselects, transactions, tons of operators! :)

>
> please correct me, if im totally wrong with my assumptions. i know quite some
> hosts running medium-to-xmedium-loaded postgres-driven websites which all have
> a vacuum-daily job in their crontab, but never heard of any complaints, due to
> this maintainace thing at night.
>

I run several of these and 30secs at 5:00am means nothing :)

> just me
> messju

regards,
Nuno Silva

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