Re: BUG #3752: query yields "could not find block containing chunk", then server crashes

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Michael Charnoky <noky(at)nextbus(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3752: query yields "could not find block containing chunk", then server crashes
Date: 2007-11-16 08:29:43
Message-ID: 473D54F7.9000305@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Do you have a core file? Can you provide stack trace output?

Thanks

Michael Charnoky wrote:
> The following bug has been logged online:
>
> Bug reference: 3752
> Logged by: Michael Charnoky
> Email address: noky(at)nextbus(dot)com
> PostgreSQL version: 8.3beta2
> Operating system: Linux (Fedora Core 3) 2.6.17
> Description: query yields "could not find block containing chunk",
> then server crashes
> Details:
>
> I installed PG8.3beta2 and created a db instance using pg_restore. (The
> dump was created using the pg8.3beta2 pg_dump util, from a db on a pg8.1
> server). Data restored with no errors, later our app encountered an sql
> error while querying data in the db. Here's the relevant log snippet:
>
> 2007-11-15 15:38:03.880 PST: ERROR: could not find block containing chunk
> 0x902fb98
> 2007-11-15 15:38:03.880 PST: STATEMENT: SELECT path_tag, dayset_tag,
> time2secs(ts_endtime), segtimes
> FROM pathtimes where rev=(select rev from projects) ORDER BY
> time2secs(ts_endtime);
> 2007-11-15 15:38:29.821 PST: LOG: server process (PID 17777) was terminated
> by signal 11: Segmentation fault
> 2007-11-15 15:38:29.821 PST: LOG: terminating any other active server
> processes
> 2007-11-15 15:38:29.825 PST: LOG: all server processes terminated;
> reinitializing
> 2007-11-15 15:38:29.887 PST: LOG: database system was interrupted; last
> known up at 2007-11-15 15:28:27 PST
> 2007-11-15 15:38:29.887 PST: LOG: database system was not properly shut
> down; automatic recovery in progress
> 2007-11-15 15:38:30.044 PST: FATAL: the database system is in recovery
> mode
> 2007-11-15 15:38:30.285 PST: LOG: record with zero length at 0/7CB47A08
> 2007-11-15 15:38:30.286 PST: LOG: redo is not required
> 2007-11-15 15:38:30.714 PST: LOG: autovacuum launcher started
> 2007-11-15 15:38:30.715 PST: LOG: database system is ready to accept
> connections
> *** glibc detected *** free(): invalid next size (normal): 0x09045378 ***
> 2007-11-15 15:38:41.463 PST: LOG: server process (PID 17811) was terminated
> by signal 6: Aborted
> 2007-11-15 15:38:41.463 PST: LOG: terminating any other active server
> processes
> 2007-11-15 15:38:41.464 PST: LOG: all server processes terminated;
> reinitializing
> 2007-11-15 15:38:41.516 PST: LOG: database system was interrupted; last
> known up at 2007-11-15 15:38:30 PST
> 2007-11-15 15:38:41.516 PST: LOG: database system was not properly shut
> down; automatic recovery in progress
> 2007-11-15 15:38:41.683 PST: LOG: record with zero length at 0/7CB47A48
> 2007-11-15 15:38:41.683 PST: LOG: redo is not required
> 2007-11-15 15:38:41.702 PST: FATAL: the database system is in recovery
> mode
> 2007-11-15 15:38:41.806 PST: LOG: autovacuum launcher started
> 2007-11-15 15:38:41.807 PST: LOG: database system is ready to accept
> connections
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Zdenek Kotala 2007-11-16 09:52:54 Re: BUG #3752: query yields "could not find block containing chunk", then server crashes
Previous Message Zdenek Kotala 2007-11-16 08:27:08 Re: BUG #3754: postgresql+hibernate