| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jules Bean | 2000-07-26 14:58:26 | Re: Performance for seq. scans |
| Previous Message | Jules Bean | 2000-07-26 14:44:47 | Re: Performance for seq. scans |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-07-26 15:09:17 | AW: AW: AW: Vacuum only with 20% old tuples |
| Previous Message | Ron Peterson | 2000-07-26 14:39:30 | Re: free auction project with Postgres |