pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steven Flatt <steven.flatt@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Insertion to temp table deteriorating over time
Date: Thu, 14 Dec 2006 16:23:16 -0500
Message-ID: <25209.1166131396@sss.pgh.pa.us> (raw)
In-Reply-To: <357fa7590612141240t55e70695q770a05a68a67536c@mail.gmail.com>
References: <357fa7590612130844q58ef3ca5q31e164f9b006e0fc@mail.gmail.com>
	<9315.1166030958@sss.pgh.pa.us>
	<357fa7590612131517q375fc0by50cb4257bcce7a94@mail.gmail.com>
	<13032.1166052447@sss.pgh.pa.us>
	<357fa7590612141240t55e70695q770a05a68a67536c@mail.gmail.com>

"Steven Flatt" <steven.flatt@gmail.com> writes:
> Regarding your other email -- interesting -- but we are vacuuming pg_class
> every hour.  So I don't think the answer lies there...

That's good, but is the vacuum actually accomplishing anything?  I'm
wondering if there's also a long-running transaction in the mix.
Try a manual "VACUUM VERBOSE pg_class;" after the thing has slowed down,
and see what it says about removable and nonremovable rows.

			regards, tom lane



view thread (22+ messages)  latest in thread

Message-ID: <25209.1166131396@sss.pgh.pa.us>
Permalink:  ../25209.1166131396@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25209.1166131396@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, steven.flatt@gmail.com
  Subject: Re: Insertion to temp table deteriorating over time
  In-Reply-To: <25209.1166131396@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