Re: Updating multiple bool values crashes backend - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Updating multiple bool values crashes backend
Date
Msg-id 5464.972569656@sss.pgh.pa.us
Whole thread Raw
In response to Re: Updating multiple bool values crashes backend  (Sean Kelly <S.Kelly@ncl.ac.uk>)
Responses Re: Updating multiple bool values crashes backend
List pgsql-bugs
Sean Kelly <S.Kelly@ncl.ac.uk> writes:
>     Ok, I sorted that ... I now have a 2Mb core file.  Can you
> explain how to 'backtrace' it with gdb ...

    gdb /path/to/postgres-executable /path/to/core-file
    bt
    quit

and send the results.  Hopefully there will be at least function names
in the display --- if it's all numbers then don't bother sending it :-(

> I've stuck the core
> file at http://www.randomfx.net/core.html if you need it.

Thanks, but it's pretty much useless to anyone who doesn't have the
exact same executable and same system platform as you.

>>>>> With respect to GCC errors, '11' normally indicates a hardware
>>>>> problem
>>
>> Uh, whoever told you that?

>     One example can be found on http://www.bitwizard.nl/sig11/

Hmph.  bitwizard may think that flaky hardware is a normal state of
affairs, but I don't.  Perhaps he buys his machines from incompetent
manufacturers.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_log
Next
From: "D. Jay Newman"
Date:
Subject: Re: Select where (upper(xy)~'.CH'); ..matches also SPACE CH