From: Scott Marlowe <smarlowe@g2switchworks.com>
To: André José Guergolet <AGuergolet@compugraf.com.br>
Cc: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-sql@postgresql.org
Subject: Re: RES: Lock Problem
Date: Thu, 24 Aug 2006 16:19:41 -0500
Message-ID: <1156454380.7223.91.camel@state.g2switchworks.com> (raw)
In-Reply-To: <3FFA1818C1550246933DEA311C39B07612304A@CGEXC03.compugraf.com.br>
References: <3FFA1818C1550246933DEA311C39B07612304A@CGEXC03.compugraf.com.br>
On Thu, 2006-08-24 at 16:12, André José Guergolet wrote:
> Sorry, I have a table with 360 rows, in this table I control the state of machines on network:
>
>
> Ip State StateDate
> 172.20.0.39 Running 2006-08-23 00:00:00
> 172.20.0.59 Running 2006-08-23 00:00:00
> 172.20.0.72 Running 2006-08-23 00:00:00
> 172.20.0.84 Running 2006-08-23 00:00:00
> 172.20.0.35 Running 2006-08-23 00:00:00
> 172.20.0.17 Running 2006-08-23 00:00:00
> 172.20.0.28 Running 2006-08-23 00:00:00
> 172.20.0.39 Running 2006-08-23 00:00:00
> 172.20.0.14 Running 2006-08-23 00:00:00
> 172.20.0.33 Running 2006-08-23 00:00:00
> 172.20.0.19 Running 2006-08-23 00:00:00
>
> 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.
>
> I list this states with a webpage. This webpage updates the list every 10 seconds. My page executes only "select * from machinestates".
>
> If I stop the updates, I never get my page stopped at the select command.
>
> I read about "DIRTY Transaction", is it the way?
> I have another solution?
I'm guessing you've got a different problem. Generally speaking, in an
MVCC database like PostgreSQL, readers don't block writers, and writers
don't block readers.
We need more info on how you're doing this. SQL queries for the updates
etc...
Are you vacuuming the database often enough? Is this table suffering
from bloat?
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: smarlowe@g2switchworks.com, AGuergolet@compugraf.com.br, ajs@crankycanuck.ca
Subject: Re: RES: Lock Problem
In-Reply-To: <1156454380.7223.91.camel@state.g2switchworks.com>
* 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