autovacuum process (PID ...) was terminated by signal 11 - Mailing list pgsql-bugs

From Brian Hirt
Subject autovacuum process (PID ...) was terminated by signal 11
Date
Msg-id 0A369EA6-330B-4DD2-81FE-88F32D88F600@mobygames.com
Whole thread Raw
Responses Re: autovacuum process (PID ...) was terminated by signal 11
List pgsql-bugs
Hi.

When I'm doing a database load of a 5gb database, autovacuum always
segfaults shortly after the load finishes.  The load is being done
via slony
during the initial copy set command while building a slave, not through
pg_restore.

LOG:  autovacuum process (PID ...) was terminated by signal 11
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server
process
DETAIL:  The postmaster has commanded this server process to roll
back the
current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.

This problem sounds similiar to these reports:

http://archives.postgresql.org/pgsql-bugs/2005-09/msg00200.php

and

http://archives.postgresql.org/pgsql-bugs/2005-11/msg00276.php


here is the stack for the autovacuum process.

Program received signal SIGSEGV, Segmentation fault.
CopySnapshot (snapshot=0x0) at tqual.c:1301
1301            newsnap = (Snapshot) palloc(sizeof(SnapshotData) +
(gdb) bt
#0  CopySnapshot (snapshot=0x0) at tqual.c:1301
#1  0x0812388c in _SPI_execute_plan (plan=0x83cd3e0, Values=0x841adf0,
     Nulls=0x841ae00 "  ", snapshot=0x0, crosscheck_snapshot=0x0,
     read_only=1 '\001', tcount=1) at spi.c:1433
#2  0x0812215a in SPI_execute_plan (plan=0x83cd3e0, Values=0x841adf0,
     Nulls=0x841ae00 "  ", read_only=1 '\001', tcount=1) at spi.c:336
#3  0x403cc0ef in ?? ()
#4  0x403c90e9 in ?? ()
#5  0x403c8668 in ?? ()
#6  0x403c84e7 in ?? ()
#7  0x403c83f1 in ?? ()
#8  0x403c7651 in ?? ()
#9  0x403c442a in ?? ()
#10 0x081137c8 in ExecMakeFunctionResult (fcache=0x83fcb88,
     econtext=0x83fcb18, isNull=0xbfffe94b "?\020???", isDone=0x0)
     at execQual.c:1095
#11 0x0811554e in ExecEvalExprSwitchContext (expression=0x83fcb88,
     econtext=0x83fcb18, isNull=0xbfffe94b "?\020???", isDone=0x0)
     at execQual.c:2864
#12 0x080b20e6 in FormIndexDatum (indexInfo=0x83ad7d0, slot=0x83fea98,
     estate=0x83fca90, values=0xbfffea10, isnull=0xbfffe9f0 "??:\b\n")
     at index.c:971
#13 0x080dd832 in compute_index_stats (onerel=0x401f6f58,
totalrows=11323,
---Type <return> to continue, or q <return> to quit---
     indexdata=0x83ad3d0, nindexes=4, rows=0x83e9940, numrows=3000,
     col_context=0x83fab88) at analyze.c:540
#14 0x080dd4b7 in analyze_rel (relid=32465292, vacstmt=0x83a48d8)
     at analyze.c:387
#15 0x08109365 in vacuum (vacstmt=0x83a48d8, relids=0x83a5540) at
vacuum.c:476
#16 0x0815b4bd in autovacuum_do_vac_analyze (relids=0x83a5540,
dovacuum=0,
     doanalyze=1, freeze=0) at autovacuum.c:907
#17 0x0815b16d in do_autovacuum (dbentry=0x82fb410) at autovacuum.c:681
#18 0x0815acb7 in AutoVacMain (argc=0, argv=0x0) at autovacuum.c:423
#19 0x0815aa01 in autovac_start () at autovacuum.c:170
#20 0x0815fe84 in ServerLoop () at postmaster.c:1269
#21 0x0815f80f in PostmasterMain (argc=2, argv=0x82d6158) at
postmaster.c:943
#22 0x0812a9fb in main (argc=2, argv=0x82d6158) at main.c:256
#23 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
(gdb)


--------------------------------------------
MobyGames
http://www.mobygames.com
The world's largest and most comprehensive
gaming database project

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2143: Indexes incorrectly created from database dump
Next
From: Tom Lane
Date:
Subject: Re: autovacuum process (PID ...) was terminated by signal 11