| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Michael Holzman <michaelholzman(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Autovacuum of independent tables |
| Date: | 2020-09-08 07:45:53 |
| Message-ID: | CAFj8pRD1=CUAhixyP5CGGsc=GOHFWX3oM22WFU6KnH1CAqN2YQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi
út 8. 9. 2020 v 9:32 odesílatel Michael Holzman <michaelholzman(at)gmail(dot)com>
napsal:
> Hi,
>
> I have two applications A and B. A runs SELECT statements only and only on
> tableA. B actively updates tableB, A never looks into tableB. B has nothing
> to do with tableA.
>
> Still, if A is inside a long running transaction, autovacuum does not
> handle tableB. Why is it so?
>
autovacuum does cleaning of changes related to finished transactions. It
does nothing if possible dead tuples are assigned to open transactions.
Regards
Pavel
>
> --
> Regards,
> Michael Holzman
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Holzman | 2020-09-08 08:16:04 | Re: Autovacuum of independent tables |
| Previous Message | Michael Holzman | 2020-09-08 07:32:36 | Autovacuum of independent tables |