From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Ted Clark <tootallted(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2197: PostgreSQL error- 'could not read block 0 of relation' |
Date: | 2010-01-13 16:48:10 |
Message-ID: | 407d949e1001130848w16d4195q8dc41024d982ef33@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
What postgres version?
In any case there is not enough information here to identify what
happened. What does "not all key references had been cleaned up" mean?
What commands did you run and what results did they have?
On Tue, Jan 12, 2010 at 4:26 PM, Ted Clark <tootallted(at)gmail(dot)com> wrote:
> BUG #2197: PostgreSQL error- 'could not read block 0 of relation'
>
> I found this bug has nothing to do with hardware. I was attemping to copy
> large amounts of data from text files into tables with a primary and many
> foreign keys. I found that upon truncating the tables not all key
> references had been cleaned up by the database asa they had been in prior
> day successful runs. After truncating all tables with a truncate table
> xxxxxx cascade and then loading back into the same table, my problem was
> resolved.
>
> -Ted
>
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-01-13 16:58:48 | Re: BUG #5269: postgres backend terminates with SIGSEGV |
Previous Message | Kevin Grittner | 2010-01-13 16:01:51 | Re: Substring auto trim |