Re: BUG #13490: Segmentation fault on pg_stat_activity - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #13490: Segmentation fault on pg_stat_activity
Date
Msg-id 11375.1437237936@sss.pgh.pa.us
Whole thread Raw
In response to BUG #13490: Segmentation fault on pg_stat_activity  (michael@bommaritollc.com)
Responses Re: BUG #13490: Segmentation fault on pg_stat_activity  (Michael Bommarito <michael@bommaritollc.com>)
List pgsql-bugs
Michael Bommarito <michael@bommaritollc.com> writes:
> Compiled from source with --debug using 9.5alpha1 with -O0 -ggdb
> -fno-omit-frame-pointer -mno-red-zone.  Reset to default postgresql.conf.
> Was able to generate segfaults repeatedly loading pghero dashboard.  First,
> some errors from the pg logs.
> 2015-07-18 15:07:58 UTC [27112-1] postgres@database ERROR:  attribute
> number 2 exceeds number of columns 0
> 2015-07-18 15:08:23 UTC [27112-3] postgres@database ERROR:  invalid
> varattno 66
> 2015-07-18 15:17:19 UTC [3605-1] postgres@database ERROR:  tupdesc
> reference 0x2bdd8a8 is not owned by resource owner Portal
> 2015-07-18 15:48:38 UTC [10281-1] postgres@database ERROR:  tupdesc
> reference 0xf77248 is not owned by resource owner Portal

I'm starting to wonder about flaky hardware and/or compiler bugs.  9.5
seems completely unreliable for you, but we're not seeing any similar
reports from anyone else.  Is 9.4 reliable on the same machine + same
build environment?

> Program received signal SIGQUIT, Quit.

Catching a SIGQUIT isn't very helpful; that just means you're one of
the server processes that got force-terminated after some other one
crashed.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #12379: pgbench should hint to pgbench -i
Next
From: Alvaro Herrera
Date:
Subject: Re: [Postgresql Master Branch Patch] object class patch