From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Mike Broers <mbroers(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] after 9.2.4 patch vacuumdb -avz not analyzing all tables |
Date: | 2013-04-12 01:32:07 |
Message-ID: | 534.1365730327@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> I believe the rationale was so that an autovacuum would still look like it
> was needed, and get fired again the next naptime, so that it could continue
> with the truncation attempts. (Rather than waiting for 20% turnover in the
> table before trying again). I'm not convinced by this argument. If the
> DBA is desperate to get the space back, they can go do vacuum full.
Well, that's why I think the lock abandonment shouldn't apply to manual
plain vacuum. You shouldn't need to do a vacuum full for that; that'd
be a huge increase in the cost, not to mention that it'd transiently
require twice the disk space, hardly a good thing if you're short.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-04-12 01:48:02 | Re: [ADMIN] after 9.2.4 patch vacuumdb -avz not analyzing all tables |
Previous Message | Julian Glass | 2013-04-12 01:28:06 | Re: Invalid SQL not rejected? |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-04-12 01:41:08 | Re: Add SPI_gettypmod() fucntion |
Previous Message | Amit Kapila | 2013-04-12 01:29:54 | Re: Add SPI_gettypmod() fucntion |