On Fri, Aug 21, 2009 at 04:26:11PM +0000, Sebastien Lardiere wrote: > > The following bug has been logged online: > > Bug reference: 5004 > Logged by: Sebastien Lardiere > Email address: slardi...@hi-media.com > PostgreSQL version: 8.3.7 > Operating system: Debian Etch > Description: pg_freespacemap make a SegFault > Details: > > I've got a crash with a cluster. Nothing found in the logfile, but a message > about a Segfault, so I get a coredump and here is the backtrace :
Can you check if you had any vacuums running at the time of crash? It might be in logs, something like: 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. HINT: In a moment you should be able to reconnect to the database and repeat your command. STATEMENT: vacuum if yes - how many vacuum jobs there were? depesz -- Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/ jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:6749007 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
