| From: | Kashif Zeeshan <kashi(dot)zeeshan(at)gmail(dot)com> |
|---|---|
| To: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, andrian(dot)klaver(at)aklaver(dot)com |
| Subject: | Re: Regarding vacuum freeze locking mechanism |
| Date: | 2024-07-18 05:28:03 |
| Message-ID: | CAAPsdhdtx61Hi-M1kV=xc1NOkT7MmyrqJ_YYxsasoJqgoFVTWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi
On Thu, Jul 18, 2024 at 10:26 AM Durgamahesh Manne <
maheshpostgres9(at)gmail(dot)com> wrote:
> Hi
>
> Do new inserts block while performing vacuum freeze operations ?
>
Generally, VACUUM FREEZE does not block inserts as PG uses Multi-Version
Concurrency Control (MVCC) which allows multiple transactions to operate on
the same table without interfering with each other.
>
> when autovacuum runs , it will freeze the transaction ID (TXID) of the
> table it's working on. This means that any transactions that started before
> autovacuum began will be allowed to complete.but new transactions will be
> blocked until the autovacuum finishes.
>
> Could you please provide more clarity on this? Which lock triggers on the
> tables are being used by freeze?
>
> Your response is highly appreciated
>
> Regards,
> Durga Mahesh
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-07-18 05:53:21 | Re: Regarding vacuum freeze locking mechanism |
| Previous Message | Durgamahesh Manne | 2024-07-18 05:27:10 | Regarding vacuum freeze locking mechanism |