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: Wed, 17 Mar 2004 12:58:09 -0500
Message-ID: <26451.1079546289@sss.pgh.pa.us> (raw)
In-Reply-To: <002a01c40c45$f736d8a0$2500fa0a@CardServices.TCI.com>
References: <002a01c40c45$f736d8a0$2500fa0a@CardServices.TCI.com>

"Rosser Schwarz" <rschwarz@totalcardinc.com> writes:
>> Could you retry the strace with -r and -T options

> Unlike the previous run (this is a trace of the explain), this one went
> immediately.  No delay.

Hm.  It looks like you mistakenly traced psql rather than the backend,
but since the delay went away we wouldn't have learned anything anyhow.
Have you got any idea what conditions may have changed between seeing
delay and not seeing delay?

> I also have, per Aaron's request, a trace -ct against the backend running
> the explain analyze.  I killed it well before "a few minutes"; it's just
> shy of 900K.  I don't think I'll be forwarding that on to the list, though
> I can put it up on a web server somewhere easily enough.
> Try <http://www.totalcardinc.com/pg/postmaster.trace;.

This is pretty odd too.  It looks like it's doing checkpoints every so
often (look for the writes to pg_control), which a backend engaged in
a long-running query surely ought not be doing.  Need to think about
why that might be...

			regards, tom lane



view thread (39+ messages)  latest in thread

Message-ID: <26451.1079546289@sss.pgh.pa.us>
Permalink:  ../26451.1079546289@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26451.1079546289@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: <26451.1079546289@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