Re: Frequently updated tables

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql(at)mohawksoft(dot)com, Mark Kirkwood <markir(at)coretech(dot)co(dot)nz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Frequently updated tables
Date: 2004-06-09 18:16:17
Message-ID: 40C753F1.5040305@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Also he said that the problem was solved with enough lazy VACUUM
> scheduling. I don't understand why he doesn't want to use that
> solution.

Because even lazy VACUUM is horrendous to performance but as I said in
a further post this has been pretty much fixed by (Jan I believe) in 7.5.

Sincerely,

Joshua D. Drake

>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

Attachment Content-Type Size
jd.vcf text/x-vcard 640 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Scott Marlowe 2004-06-09 18:26:27 Re: Frequently updated tables
Previous Message Joshua D. Drake 2004-06-09 18:14:51 Re: Frequently updated tables