From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: spgist recovery assertion failure |
Date: | 2015-07-27 05:29:41 |
Message-ID: | 20150727052941.GG1504258@tornado.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 27, 2015 at 02:19:09PM +0900, 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 saw it on ppc64 Fedora and on {ppc32 PostgreSQL, ppc64 kernel} AIX. Like
you, I don't see it on x86_64 Ubuntu. Perhaps it is specific to big-endian.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2015-07-27 05:31:39 | Re: LWLock deadlock and gdb advice |
Previous Message | Michael Paquier | 2015-07-27 05:19:09 | Re: spgist recovery assertion failure |