Skip site navigation (1) Skip section navigation (2)

BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update

From: "Henry" <henka(at)cityweb(dot)co(dot)za>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5736: 9.0.1 segmentation fault (sig11) during long-lived update
Date: 2010-10-30 19:18:59
Message-ID: 201010301918.o9UJIxIc015004@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5736
Logged by:          Henry
Email address:      henka(at)cityweb(dot)co(dot)za
PostgreSQL version: 9.0.1
Operating system:   Linux
Description:        9.0.1 segmentation fault (sig11) during long-lived
update
Details: 

Hi,

I'm using PostgreSQL 9.0.1 on centos 5.4.

I'm running the following update (which takes a few days to run before I get
the error - twice now):

update tab1 set col1 = hashtext(col0) where col1 isnull;

I'm running this update as part of an exercise to purge duplicates, before
creating a UNIQUE index.

Error from PG:

server process (PID 19328) was terminated by signal 11: Segmentation fault
terminating any other active server processes
...

Before I run this again, what's the best way to proceed to get a core dump
so I can run a gdb backtrace to provide more info?  Simply 'ulimit -c
5242880' as user postgres and restart PG?

Thanks

Responses

pgsql-bugs by date

Next:From: Greg StarkDate: 2010-10-30 19:19:31
Subject: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."
Previous:From: Gary DoadesDate: 2010-10-30 18:32:20
Subject: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group