| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Stephen Froehlich <s(dot)froehlich(at)cablelabs(dot)com> |
| Cc: | "Greg Rychlewski (LCL)" <Greg(dot)Rychlewski(at)loblaw(dot)ca>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Does cancelling autovacuum make you lose all the work it did? |
| Date: | 2020-06-12 17:56:08 |
| Message-ID: | CAKFQuwZc7YjsLXZwMws9+wLA828RkYbiABfDtMJuqNL==F34Dg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
The custom here is to inline or bottom-post.
On Fri, Jun 12, 2020 at 10:41 AM Stephen Froehlich <
s(dot)froehlich(at)cablelabs(dot)com> wrote:
> No autovacuum or vacuum causes no user-visible or breaking changes of any
> kind … it does change the performance of the database backend, but that’s
> all.
>
Um...doesn't really answer the question and besides hitting the wrap-around
limit causes the server to not start in multi-user mode which is surely a
user-visible effect. Performance is a user-visible effect too - the only
thing it better not impact is the correctness of the results.
To answer the original question: vacuum's effects are basically immediate
so work is not lost if it gets cancelled.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-06-12 20:33:46 | Re: Does cancelling autovacuum make you lose all the work it did? |
| Previous Message | Stephen Froehlich | 2020-06-12 17:40:45 | RE: Does cancelling autovacuum make you lose all the work it did? |