From: Luke Lonergan <llonergan@greenplum.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew Schumacher <matt.s@aptalaska.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance problems testing with Spamassassin
Date: Fri, 29 Jul 2005 12:02:30 -0700
Message-ID: <BF0FCB56.A410%llonergan@greenplum.com> (raw)
In-Reply-To: <20875.1122531559@sss.pgh.pa.us>
Tom,
On 7/27/05 11:19 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
> Matthew Schumacher <matt.s@aptalaska.net> writes:
>> After playing with various indexes and what not I simply am unable to
>> make this procedure perform any better. Perhaps someone on the list can
>> spot the bottleneck and reveal why this procedure isn't performing that
>> well or ways to make it better.
>
> There's not anything obviously wrong with that procedure --- all of the
> updates are on primary keys, so one would expect reasonably efficient
> query plans to get chosen. Perhaps it'd be worth the trouble to build
> the server with profiling enabled and get a gprof trace to see where the
> time is going.
Yes - that would be excellent. We've used oprofile recently at Mark Wong's
suggestion, which doesn't require rebuilding the source.
- Luke
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: llonergan@greenplum.com, tgl@sss.pgh.pa.us, matt.s@aptalaska.net
Subject: Re: Performance problems testing with Spamassassin
In-Reply-To: <BF0FCB56.A410%llonergan@greenplum.com>
* 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