Re: spgist recovery assertion failure

From: Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: spgist recovery assertion failure
Date: 2015-07-27 05:33:58
Message-ID: BLU436-SMTP587A1B831FE638948CFEF2F28E0@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/27/2015 07:19 AM, Michael Paquier wrote:
> On Mon, Jul 27, 2015 at 2:00 PM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>> When I caused a crash during the create_index regression test, recovery hit an
>> assertion failure. Minimal test case:
>>
>> psql -X <<EOSQL
>> CREATE TABLE t (c text);
>> INSERT INTO t SELECT 'P0123456789abcdef' FROM generate_series(1,1000);
>> INSERT INTO t VALUES ('P0123456789abcdefF');
>> CREATE INDEX ON t USING spgist (c);
>> EOSQL
>> pg_ctl -m immediate -w restart
>
> On which platform are you seeing the failure? I am afraid I could not
> reproduce the failure on Linux and OSX after testing it on HEAD.
>

I'm having the same symptoms with
159cff58cf3b565be3c17901698a74238e9e23f8 on Ubuntu Linux 3.4.39 armv7l.

Attachment Content-Type Size
parentBlk-assertion-failure.txt text/plain 3.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2015-07-27 05:34:11 Re: Sharing aggregate states between different aggregate functions
Previous Message Amit Langote 2015-07-27 05:31:39 Re: LWLock deadlock and gdb advice