Re: segfault with expression index, btree_gist and HOT Update - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: segfault with expression index, btree_gist and HOT Update
Date
Msg-id 20181107144957.rxhrkbiribnh7yvg@alvherre.pgsql
Whole thread Raw
In response to segfault with expression index, btree_gist and HOT Update  (Tobias Bussmann <t.bussmann@gmx.net>)
List 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.
Testingrevealed the crash is still present in last week's master branch but not in 10. I further simplified the test
caseto:
 
> 
> 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
indexeswhich 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


pgsql-bugs by date:

Previous
From: Tobias Bussmann
Date:
Subject: segfault with expression index, btree_gist and HOT Update
Next
From: Tom Lane
Date:
Subject: Re: BUG #15466: Logical backups from v10 cannot be restored with v11 - "ERROR: schema "public" already exists"