| 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:04:00 |
| Message-ID: | CANtu0oi0rkR+FsgyLXnGZ-uW2950-urApAWLhy-+V1WJD=_ZXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello everyone, and Mathias!
I have fixed sp-gist related crash and a few issues in implementation.
Now it passes tests and (in my opinion) feels simpler.
I'll register that thread in commitfest to honor the bureaucracy.
Best regards,
Mikhail.
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0003-This-should-fix-issues-with-incorrect-results-whe.patch | application/octet-stream | 10.6 KB |
| v6-0002-Also-add-ability-to-set-LP_DEAD-bits-in-more-case.patch | application/octet-stream | 2.6 KB |
| v6-0001-This-should-fix-issues-with-incorrect-results-whe.patch | application/octet-stream | 10.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2025-02-05 10:11:40 | Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM? |
| Previous Message | Daniel Gustafsson | 2025-02-05 10:00:24 | Re: Special-case executor expression steps for common combinations |