| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | List pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Is autovacuum doing a wraparound-avoiding VACUUM? |
| Date: | 2008-07-16 16:55:39 |
| Message-ID: | 1216227339.19656.364.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Is autovacuum doing a wraparound-avoiding VACUUM?
Currently, no easy way to tell.
Patch to change message of autovac in pg_stat_activity when we are
performing an anti-wraparound VACUUM.
We will then be able to explain why an autovacuum process doesn't get
cancelled, like we might otherwise hope it would be.
That way we can tell difference between hung and just important.
Perhaps message should say "non-automatically cancelled VACUUM
<tablename>", but that sounded more obscure than the phrase I selected.
Discuss...
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| Attachment | Content-Type | Size |
|---|---|---|
| wraparound_msg.v1.patch | text/x-patch | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | daveg | 2008-07-17 02:44:07 | Re: pg_dump lock timeout |
| Previous Message | daveg | 2008-07-16 12:37:36 | Re: [PATCHES] pg_dump lock timeout |