Re: BUG #13490: Segmentation fault on pg_stat_activity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Bommarito <michael(at)bommaritollc(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13490: Segmentation fault on pg_stat_activity
Date: 2015-07-18 16:45:36
Message-ID: 11375.1437237936@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Bommarito <michael(at)bommaritollc(dot)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(at)database ERROR: attribute
> number 2 exceeds number of columns 0
> 2015-07-18 15:08:23 UTC [27112-3] postgres(at)database ERROR: invalid
> varattno 66
> 2015-07-18 15:17:19 UTC [3605-1] postgres(at)database ERROR: tupdesc
> reference 0x2bdd8a8 is not owned by resource owner Portal
> 2015-07-18 15:48:38 UTC [10281-1] postgres(at)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2015-07-18 20:19:15 Re: Lack of Sanity Checking in file 'pctcl.c' for PostgreSQL 9.4.x
Previous Message Tom Lane 2015-07-18 16:32:31 Re: BUG #12379: pgbench should hint to pgbench -i