From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tobias Bussmann <t(dot)bussmann(at)gmx(dot)net> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Jürg Senn <juerg(dot)senn(at)scnat(dot)ch> |
Subject: | Re: segfault with expression index, btree_gist and HOT Update |
Date: | 2018-11-07 14:49:57 |
Message-ID: | 20181107144957.rxhrkbiribnh7yvg@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2018-Nov-07, Tobias Bussmann wrote:
> Hello,
>
> my colleague Jürg Senn recently found a backend crash in Postgres 11 and trimmed it down to a reproducible test case. Testing revealed the crash is still present in last week's master branch but not in 10. I further simplified the test case to:
>
> CREATE EXTENSION btree_gist;
> CREATE TABLE segfault (i int);
> CREATE INDEX ON segfault USING gist ((i + 10));
> INSERT INTO segfault VALUES (1);
> UPDATE segfault SET i = 2;
>
> Our tests were performed on macOS: PostgreSQL 12devel on x86_64-apple-darwin17.7.0, compiled by Apple LLVM version 9.1.0 (clang-902.0.39.2), 64-bit
>
> Apparently the segfault happens within the check for the possibility of HOT Updates with expression / functional indexes which was added by c203d6cf8 in 11.
Yeah, this code was disabled yesterday :-( Updating to current tip of
either branch should "fix" it.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-11-08 00:54:25 | Re: BUG #15466: Logical backups from v10 cannot be restored with v11 - "ERROR: schema "public" already exists" |
Previous Message | Tobias Bussmann | 2018-11-07 14:46:46 | segfault with expression index, btree_gist and HOT Update |