pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: André José Guergolet <AGuergolet@compugraf.com.br>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: RES: Lock Problem
Date: Fri, 25 Aug 2006 00:29:54 -0400
Message-ID: <18308.1156480194@sss.pgh.pa.us> (raw)
In-Reply-To: <1156454380.7223.91.camel@state.g2switchworks.com>
References: <3FFA1818C1550246933DEA311C39B07612304A@CGEXC03.compugraf.com.br>
	<1156454380.7223.91.camel@state.g2switchworks.com>

Scott Marlowe <smarlowe@g2switchworks.com> writes:
> On Thu, 2006-08-24 at 16:12, André José Guergolet wrote:
>> My system, checks if my script is running in each machine at this table, this table has 360 rows and has 50-100 updates per minute in columns STATE and STATEDATE.

> Are you vacuuming the database often enough?  Is this table suffering
> from bloat?

That's my bet.  With numbers like those, that table has to get vacuumed
every few minutes to keep performance from going into the tank.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <18308.1156480194@sss.pgh.pa.us>
Permalink:  ../18308.1156480194@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/18308.1156480194@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-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, smarlowe@g2switchworks.com, AGuergolet@compugraf.com.br, ajs@crankycanuck.ca
  Subject: Re: RES: Lock Problem
  In-Reply-To: <18308.1156480194@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