| From: | Michael Holzman <michaelholzman(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(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 08:16:04 |
| Message-ID: | CAPNViJrFNA8xiEgFeDoZ1GVKndx-MQXsES0Lg2hzrkNohzfJSA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Sep 8, 2020 at 10:46 AM Pavel Stehule wrote:
>
> autovacuum does cleaning of changes related to finished transactions. It
> does nothing if possible dead tuples are assigned to open transactions.
>
This is the point.
Autovacuum does not clean dead tuples of closed transactions in tableB
while there is an open transaction on tableA.
But the tables have nothing in common. They are handled by separate
applications and there are no transactions that touch both tables
simultaneously.
Why does autovacuum create an artificial dependency on the tables?
--
Regards,
Michael Holzman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-09-08 08:27:55 | Re: Autovacuum of independent tables |
| Previous Message | Pavel Stehule | 2020-09-08 07:45:53 | Re: Autovacuum of independent tables |