Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?

From: Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>
To: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-hackers(at)lists(dot)postgresql(dot)org, hlinnaka(at)iki(dot)fi, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?
Date: 2025-02-05 10:11:40
Message-ID: CANtu0oi_u=Y7tdT=mnAzJqdh1vEYozR_tdbpbPR7093tfDY00g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ooops, missed one commit - fixed (logic related to LP_DEAD in GIST
extracted to separate commit).

Also, commitfest entry is here - https://commitfest.postgresql.org/52/5542/

>

Attachment Content-Type Size
v7-0004-This-should-fix-issues-with-incorrect-results-whe.patch application/octet-stream 10.6 KB
v7-0002-This-should-fix-issues-with-incorrect-results-whe.patch application/octet-stream 10.3 KB
v7-0003-Also-add-ability-to-set-LP_DEAD-bits-in-more-case.patch application/octet-stream 2.6 KB
v7-0001-isolation-tester-showing-broken-index-only-scans-.patch application/octet-stream 11.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilia Evdokimov 2025-02-05 10:15:51 Re: Sample rate added to pg_stat_statements
Previous Message Michail Nikolaev 2025-02-05 10:04:00 Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?