Skip site navigation (1) Skip section navigation (2)

Re: Is Pg 7.0.x's Locking Mechanism BROKEN?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabrice Scemama <fabrice(at)scemama(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Is Pg 7.0.x's Locking Mechanism BROKEN?
Date: 2000-07-26 14:46:27
Message-ID: 10883.964622787@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Fabrice Scemama <fabrice(at)scemama(dot)org> writes:
> With 7.0.x versions, we've come across a problem, new for us:
> very often (2 or 3 times a day), there are on our Pg machine
> a dozen of 'update waiting', and our perl scripts are waiting
> too to begin a transaction.

Can you list exactly what *all* the backends are doing when this
happens?  It might help to run the postmaster with -d2 so that
the postmaster log contains a trace of all queries executed.

> - Am I the only one here to have such problems with 7.0.2?

Haven't seen any other such reports.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Zeugswetter Andreas SBDate: 2000-07-26 15:09:17
Subject: AW: AW: AW: Vacuum only with 20% old tuples
Previous:From: Ron PetersonDate: 2000-07-26 14:39:30
Subject: Re: free auction project with Postgres

pgsql-general by date

Next:From: Jules BeanDate: 2000-07-26 14:58:26
Subject: Re: Performance for seq. scans
Previous:From: Jules BeanDate: 2000-07-26 14:44:47
Subject: Re: Performance for seq. scans

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group