| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: amcheck verification for GiST |
| Date: | 2019-04-02 21:26:06 |
| Message-ID: | CAH2-Wzmh74tKkcTwmnxirY+Dj23C_0RKkwbB1bD768Le3r70LQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 28, 2019 at 11:30 PM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> Here's updated patch with AccessShareLock.
> I've tried to stress this with combination of random inserts, vaccuums and checks. This process neither failed, nor deadlocked.
> The patch intentionally contains one superflous line to make gist logically broken. This triggers regression test of amcheck.
Any thoughts on this, Heikki?
It would be nice to be able to squeeze this into Postgres 12,
especially given that GiST has been enhanced for 12 already.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pantilimonov misha | 2019-04-02 21:53:31 | Re: [GSoC] application ideas |
| Previous Message | Fred .Flintstone | 2019-04-02 21:24:44 | Re: PostgreSQL pollutes the file system |