pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Carlos Moreno <moreno_pg@mochima.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Possible explanations for catastrophic performace deterioration?
Date: Sun, 23 Sep 2007 13:27:35 -0400
Message-ID: <21428.1190568455@sss.pgh.pa.us> (raw)
In-Reply-To: <36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com>
References: <46F6981B.1010600@mochima.com>
	<36e682920709230956p1312745eif1c6ba7a342dae3d@mail.gmail.com>

"Jonah H. Harris" <jonah.harris@gmail.com> writes:
> My guess is that a vacuum full would've brought the other database
> back up to speed.

Yeah, table bloat is what it sounds like to me too.

> In the future, you probably want to set fillfactor
> to a reasonable amount to account for updates-to-blocks-between-vacuum
> to try and capture as few row-migrations as possible.

More to the point, check your FSM size and make sure vacuums are
happening often enough.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <21428.1190568455@sss.pgh.pa.us>
Permalink:  ../21428.1190568455@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21428.1190568455@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, jonah.harris@gmail.com, moreno_pg@mochima.com
  Subject: Re: Possible explanations for catastrophic performace deterioration?
  In-Reply-To: <21428.1190568455@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