Hi David.
Excellent response from you .Great
Regards,
Durga Mahesh
On Thu, Jul 18, 2024 at 11:28 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wednesday, July 17, 2024, Durgamahesh Manne
> wrote:
>
>>
>> Could you please provide more clarity on this? Which lock triggers on the
On Wednesday, July 17, 2024, Durgamahesh Manne
wrote:
>
> Could you please provide more clarity on this? Which lock triggers on the
> tables are being used by freeze?
>
https://www.postgresql.org/docs/current/explicit-locking.html
Share update exclusive
David J.
On Wednesday, July 17, 2024, Durgamahesh Manne
wrote:
> when autovacuum runs , it will freeze the transaction ID (TXID) of the
> table it's working on.
>
This statement is incorrect. A table as a whole does not have a txid.
Freezing makes it so individual tuples get assigned an always-in-the-pa
Hi
On Thu, Jul 18, 2024 at 10:26 AM Durgamahesh Manne <
maheshpostgr...@gmail.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 transacti
Hi
Do new inserts block while performing vacuum freeze operations ?
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