| From: | "PriceGoblin Accounts" <accounts(at)pricegoblin(dot)co(dot)uk> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Should autovacuum do a database wide vacuum near transaction limit? |
| Date: | 2011-01-22 09:46:33 |
| Message-ID: | E1EDB59A3C4E4ACE915899E5A5FC3B36@squarepi.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>> Was this expected behaviour with temporary tables?
>It's more expected behavior when you have long running transactions.
>I haven't seen it caused by temp tables. Was the parent process in a
>really long transaction or just open a long time without one?
The first thing I checked was for open transactions, but alas there were
none. I suspect the process had been
open a long time without creating any transactions, but don't know which
process it was at this point, the connection
was owned by my colleague so need to check with him or look for dead
applications...
John
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Lister | 2011-01-22 12:13:25 | Re: Should autovacuum do a database wide vacuum near transaction limit? |
| Previous Message | Scott Marlowe | 2011-01-22 09:36:25 | Re: Should autovacuum do a database wide vacuum near transaction limit? |