Re: Cannot start Postgres- FATAL: invalid cache id: 19 - Mailing list pgsql-general

From Jolles, Peter M (GE Energy)
Subject Re: Cannot start Postgres- FATAL: invalid cache id: 19
Date
Msg-id E66B1BA008C7374390C6AE9EF01E584A03B5CEF9@ALPMLVEM08.e2k.ad.ge.com
Whole thread Raw
In response to Re: Cannot start Postgres- FATAL: invalid cache id: 19  (Vick Khera <vivek@khera.org>)
Responses Re: Cannot start Postgres- FATAL: invalid cache id: 19  (Vick Khera <vivek@khera.org>)
List pgsql-general
On Wednesday, December 01, 2010 1:27 PM Vick Khera wrote:
> Just how big is the table and how many transactions per second do you
push
> through it?  Perhaps your I/O bandwidth is just insufficient for your
load
> level.
>

The entire database is about 700 GB. In the database I've got
approximately 1200 tables, most in the 300-500 mb range (254 columns,
500k to 1000k rows). When a table is being accessed it has approximately
5-7 transactions/sec. Usually 10-12 tables are being accessed at a time.
Each table is hit 2-3 times a day for about 10 minutes each time.

I know I/O is an issue, but I didn't expect the database to fail, and
then be what I presume to be unrecoverable. Is there a way to recover
data if I can't get Postgres to start up? Is there a way to vacuum the
table if Postgres won't start up in hopes to get it to restart? I had
the database replicated, but the copy won't start up for the same
reason.

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: How to find correct locale name for CREATE DATABASE
Next
From: "Brent Wood"
Date:
Subject: Re: techniques for bulk load of spatial data