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

Re: BUG #3595: Segmentation fault with a simple select query

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Jukka Holappa" <jukkaho(at)mail(dot)student(dot)oulu(dot)fi>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #3595: Segmentation fault with a simple select query
Date: 2007-09-03 18:06:22
Message-ID: 46DC4D1E.6000001@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Jukka Holappa wrote:
> I can't easily reproduce this problem but it happens in every few hours in
> my use.

Can you get a core dump and/or a stack trace out of it? I noted that
you're running Gentoo, so recompiling with --enable-debug, if it's not
compiled with it already, shouldn't be a problem :). --enable-cassert
could be helpful as well, though that does have an impact on performace.

Let me know if you need help compiling or getting a core dump or stack
trace with gdb.

> I'm a bit loss about what could cause this. Is there a way to check the
> current database for possible corruption? Regular queries seem to work ok.

Not really. If the query that crashed works when ran after restart, it's
not likely that corruption caused the crash. You could take a backup
with pg_dump; that at least scans through all data, so if something is
corrupted in a table it will complain.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: Ben KimDate: 2007-09-03 20:30:27
Subject: Re: BUG #3591: autovacuum crash
Previous:From: Ciprian Dorin CraciunDate: 2007-09-03 17:13:40
Subject: BUG #3596: "insert ... returning *" not usable as last statement in a function...

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