| From: | Harold Falkmeyer <hfalkmeyer(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: VACUUM ANALYZE Issues |
| Date: | 2017-06-10 02:21:59 |
| Message-ID: | CACcYrisy-cLfUrcAkgq3TmEuqhoRNk34MR3voFZAM-LJqSTL5A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Jun 8, 2017 at 10:25 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> It does so when truncating the relation, to remove free space at the end
> of the relation. If there's a lot of free space, that can take a while.
> This has been much improved in releases since 8.4.
>
Thank you for this information. Is it correct to assume that the VACUUM
would NOT release its AccessExclusive lock during a vacuum_cost_delay
sleep? Other than reading the PostgreSQL manual regarding Routine
Vacuuming and the SQL reference for VACUUM, are there other documents or
books you could recommend that would cover VACUUM internals (other than
attempting to read source :-) )?
Thank you again,
Harold Falkmeyer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | x_hsky | 2017-06-12 02:09:21 | PG-10.0 Distributed Cluster |
| Previous Message | John Scalia | 2017-06-09 13:36:07 | SSL certificate revocation file will not load |