pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Reece Hart <rkh@gene.COM>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: SF PostgreSQL <sfpug@postgresql.org>
Subject: Re: [PERFORM] slow table updates
Date: 23 Jul 2003 10:44:36 -0700
Message-ID: <1058982275.7281.83.camel@tallac> (raw)
In-Reply-To: <200307230949.10028.dev@archonet.com>
References: <1058920801.7281.67.camel@tallac>
	<200307230949.10028.dev@archonet.com>

Richard-

Thanks for the suggestions. I too had thought about the FK checks, even
though the columns aren't getting updated.

I'm flabbergasted that the update is still running (~22 hours elapsed).
By comparison, the database takes only 4 hours to recreate from backup!
Something funny is happening here. I just interrupted the update and
will find another way.

But hang on, what's this:

  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
30164 compbio   25   0  6056 6056  3568 R    98.8  0.1  29:55 postgres: admin csb [local] COPY


I am the only user and I'm not doing a copy... this must be part of the
update process. Does anyone out there know whether updates do a table
copy instead of in-table udpating (perhaps as a special case for
whole-table updates)?

Of course, I can't help but wonder whether I just killed it when it was
nearly done...

Thanks,
Reece


-- 
Reece Hart, Ph.D.                       rkh@gene.com, http://www.gene.com/
Genentech, Inc.                         650/225-6133 (voice), -5389 (fax)
Bioinformatics and Protein Engineering
1 DNA Way, MS-93                        http://www.in-machina.com/~reece/
South San Francisco, CA  94080-4990     reece@in-machina.com, GPG: 0x25EC91A0

view thread (5+ messages)  latest in thread

Message-ID: <1058982275.7281.83.camel@tallac>
Permalink:  ../1058982275.7281.83.camel@tallac/
Also on:    postgresql.org/message-id/1058982275.7281.83.camel@tallac

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: rkh@gene.COM, dev@archonet.com, pgsql-admin@postgresql.org, sfpug@postgresql.org
  Subject: Re: [PERFORM] slow table updates
  In-Reply-To: <1058982275.7281.83.camel@tallac>
  References: <1058920801.7281.67.camel@tallac> <200307230949.10028.dev@archonet.com> <1058982275.7281.83.camel@tallac>

* 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