pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rosser Schwarz <rschwarz@totalcardinc.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: atrocious update performance
Date: Tue, 16 Mar 2004 17:29:53 -0500
Message-ID: <294.1079476193@sss.pgh.pa.us> (raw)
In-Reply-To: <001f01c40ba4$a3810420$2500fa0a@CardServices.TCI.com>
References: <001f01c40ba4$a3810420$2500fa0a@CardServices.TCI.com>

"Rosser Schwarz" <rschwarz@totalcardinc.com> writes:
> Having never more than glanced at the output of "vacuum verbose", I
> can't say whether that makes the cut for oodles.  My suspicion is no.

Nope, it sure doesn't.  We occasionally see people who don't know they
need to vacuum regularly and have accumulated hundreds or thousands of
dead tuples for every live one :-(.  That's clearly not the issue here.

I'm fresh out of ideas, and the fact that this is a live server kinda
limits what we can do experimentally ... but clearly, *something* is
very wrong.

Well, when you don't know what to look for, you still have to look.
One possibly useful idea is to trace the kernel calls of the backend
process while it does that ridiculously long EXPLAIN --- think you could
try that?

			regards, tom lane



view thread (39+ messages)  latest in thread

Message-ID: <294.1079476193@sss.pgh.pa.us>
Permalink:  ../294.1079476193@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/294.1079476193@sss.pgh.pa.us

 · 

reply

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, rschwarz@totalcardinc.com
  Subject: Re: atrocious update performance
  In-Reply-To: <294.1079476193@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