Re: RES: Lock Problem
От | Scott Marlowe |
---|---|
Тема | Re: RES: Lock Problem |
Дата | |
Msg-id | 1156454380.7223.91.camel@state.g2switchworks.com обсуждение исходный текст |
Ответ на | RES: Lock Problem (André José Guergolet <AGuergolet@compugraf.com.br>) |
Ответы |
Re: RES: Lock Problem
|
Список | pgsql-sql |
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 updatesper 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 * frommachinestates". > > 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?
В списке pgsql-sql по дате отправления: