From: Tom Lane <tgl@sss.pgh.pa.us>
To: Luke Lonergan <LLonergan@greenplum.com>
Cc: Andrew McMillan <andrew@catalyst.net.nz>
Cc: Matthew Schumacher <matt.s@aptalaska.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance problems testing with Spamassassin
Date: Fri, 29 Jul 2005 10:12:46 -0400
Message-ID: <16614.1122646366@sss.pgh.pa.us> (raw)
In-Reply-To: <3E37B936B592014B978C4415F90D662D0C4221@MI8NYCMAIL06.Mi8.com>
References: <3E37B936B592014B978C4415F90D662D0C4221@MI8NYCMAIL06.Mi8.com>
"Luke Lonergan" <LLonergan@greenplum.com> writes:
> I guess we see the real culprit here. Anyone surprised it's the WAL?
You have not proved that at all.
I haven't had time to look at Matthew's problem, but someone upthread
implied that it was doing a separate transaction for each word. If so,
collapsing that to something more reasonable (say one xact per message)
would probably help a great deal.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, LLonergan@greenplum.com, andrew@catalyst.net.nz, matt.s@aptalaska.net
Subject: Re: Performance problems testing with Spamassassin
In-Reply-To: <16614.1122646366@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox