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

seg fault crashed the postmaster

From: Gordon Shannon <gordo169(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: seg fault crashed the postmaster
Date: 2010-12-31 00:52:45
Message-ID: 1293756765858-3323117.post@n5.nabble.com (view raw or flat)
Thread:
Lists: pgsql-general
Hi,

Running Centos, just upgraded our production db from 8.4.4 to 9.0.2 last
night.  About 20 hours later, an update statement seg faulted and crashed
the server. This is a typical update that has worked fine for a long time.

20898 datafeed (58628) 2010-12-30 19:28:14 EST [103]LOG:  process 20898
acquired ShareLock on transaction 1286738762 after 90174.969 ms
20898 datafeed (58628) 2010-12-30 19:28:14 EST [104]STATEMENT:  update
v_messages set status = 'S', updated_on = now() where id in (select id from
v_messages where author_id = 34409854 and status != 'S' limit 10000)
5802   2010-12-30 19:28:14 EST [4]LOG:  server process (PID 20898) was
terminated by signal 11: Segmentation fault
5802   2010-12-30 19:28:14 EST [5]LOG:  terminating any other active server
processes
15426 pipeline (36834) 2010-12-30 19:28:14 EST [1]WARNING:  terminating
connection because of crash of another server process15426 pipeline
10.10.11.54(36834) 2010-12-30 19:28:14 EST [2]DETAIL:  The postmaster has
commanded this server process to roll back the current transaction and exit,
because another server pro
cess exited abnormally and possibly corrupted shared memory.

One hint that something might be wrong was this:

18235 datafeed (44228) 2010-12-30 18:16:37 EST [11]LOG:  process 18235
acquired ShareLock on transaction 1285952031 after 29966.703 ms
18235 datafeed (44228) 2010-12-30 18:16:37 EST [12]STATEMENT:  update
v_messages set status = 'S', updated_on = now() where id in (select id from
v_messages where author_id = 25301995 and status != 'S' limit 10000)
18235 datafeed (44228) 2010-12-30 18:16:43 EST [13]ERROR:  compressed data
is corrupt
18235 datafeed (44228) 2010-12-30 18:16:43 EST [14]STATEMENT:  update
v_messages set status = 'S', updated_on = now() where id in (select id from
v_messages where author_id = 25301995 and status != 'S' limit 10000)

How concerned should I be?  Thanks!

Gordon

-- 
View this message in context: http://postgresql.1045698.n5.nabble.com/seg-fault-crashed-the-postmaster-tp3323117p3323117.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Responses

pgsql-general by date

Next:From: Elliot ChanceDate: 2010-12-31 01:19:51
Subject: Fwd: Postgres forums ... take 2
Previous:From: John R PierceDate: 2010-12-30 21:43:54
Subject: Re: The system cannot execute the specified program in windows xp (service pack 3)

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