From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
---|---|
To: | Kenneth Marshall <ktm(at)rice(dot)edu> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Reduction in WAL for UPDATEs |
Date: | 2007-03-28 13:51:45 |
Message-ID: | 460A72F1.6080909@phlo.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kenneth Marshall wrote:
> We use DSPAM as one of our anti-spam options. Its UPDATE pattern is to
> increment a spam counter or a not-spam counter while keeping the user and
> token information the same. This would benefit from this optimization.
> Currently we are forced to use MySQL with MyISM tables to support the
> update load, although PostgreSQL 8.2 performance is right at the I/O
> break-even point for switching databases. With HOT and more optimized
> UPDATE I/O, 8.3 would give us enough I/O headroom to switch to PostgreSQL.
Interesting. I've switched from MySQL to PostgreSQL for dspam, because
of concurrency issues with MyISAM which caused bad performance.
I am eager to see how much HOT speeds of my setup, though ;-)
BTW, the "COMMIT NOWAIT" feature Simon Riggs proposed should provide
a huge speedup too, since dspam runs one transaction for each token
it has to update.
greetings, Florian Pflug
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-28 14:51:43 | Re: Reduction in WAL for UPDATEs |
Previous Message | Tom Lane | 2007-03-28 13:46:30 | Re: Reduction in WAL for UPDATEs |