| From: | Tobias Brox <tobias(at)nordicbet(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | long running transactions |
| Date: | 2006-10-10 16:10:27 |
| Message-ID: | 20061010161027.GA18908@oppetid.no |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
While doing a verbose vacuum, I'm constantly hitting things like:
DETAIL: 3606 dead row versions cannot be removed yet.
I believe this is a problem, because I still do have some empty tables
requireing up to 3-400 ms just to check if the table is empty (see
thread "slow queue-like empty table").
If pg_stat_activity.query_start actually is the start time of the
transaction, then we've gotten rid of all the real long-running
transactions. Then again, if pg_stat_activity.query_start actually was
the start time of the transaction, the attribute would have been called
pg_stat_activity.transaction_start, right?
Is there any way to find the longest running transaction?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-10-10 16:10:41 | Re: [PERFORM] Postgre 8.0 Installation - Issues |
| Previous Message | Bill Moran | 2006-10-10 15:26:39 | Re: [PERFORM] Postgre 8.0 Installation - Issues |