The following bug has been logged online:

Bug reference: 2142
Logged by: Brian Hirt
Email address: bhirt@mobygames.com
PostgreSQL version: 8.1.1
Operating system: redhat 7.3
Description: autovacuum process (PID 1641) was terminated by signal
11
Details:

When I'm doing a database load of a 5gb database, autovacuum always
segfaults shortly after the load finishes

LOG: autovacuum process (PID 1641) 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.

I'll try to get around to recompiling with debug and running from gdb to get
a back trace.

This problem sounds similiar to these reports:

http://archives.postgresql.org/pgsql...9/msg00200.php

and

http://archives.postgresql.org/pgsql...1/msg00276.php

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Please disregard. I submitted last night via the web and when it
didn't go through I joined the list and sent again. I guess it was
just slow to go through.

Thanks again to everyone who earlier today.

--brian

On Jan 3, 2006, at 10:52 PM, Brian Hirt wrote:

>
> The following bug has been logged online:
>
> Bug reference: 2142
> Logged by: Brian Hirt
> Email address: bhirt@mobygames.com
> PostgreSQL version: 8.1.1
> Operating system: redhat 7.3
> Description: autovacuum process (PID 1641) was terminated by
> signal
> 11
> Details:
>
> When I'm doing a database load of a 5gb database, autovacuum always
> segfaults shortly after the load finishes
>
> LOG: autovacuum process (PID 1641) 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.
>
> I'll try to get around to recompiling with debug and running from
> gdb to get
> a back trace.
>
> This problem sounds similiar to these reports:
>
> http://archives.postgresql.org/pgsql...9/msg00200.php
>
> and
>
> http://archives.postgresql.org/pgsql...1/msg00276.php
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org

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


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org