From: | hikkis21c(at)hotmail(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #10338: could not read block |
Date: | 2014-05-16 07:20:39 |
Message-ID: | 20140516072039.16848.66070@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 10338
Logged by: seowoong KIM
Email address: hikkis21c(at)hotmail(dot)com
PostgreSQL version: 9.1.3
Operating system: windows 8 64bit
Description:
Hi,
I faced some problem with postgresql server.
there were some errors like
"could not read block 0 in file "base/16393/18592": read only 0 of 8192
bytes"
and some primary key relate with 18592 file
and from other key same problem happen.
this problem happen when I try to insert some data.
I use default configurations.
I have to recovery quicky, so I dump all data and schema and make new
database schema and restore dump file
after restore I work well.
I want to know why some file change to 0 byte file.
when I search this problem, I saw some different persons faced same
problem.
but, some responses are hardware problem.
so, is it really hardware problem??
please response this problem
thanks & best regards
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2014-05-16 08:23:19 | Re: Re: [BUGS] BUG #10250: pgAdmin III 1.16.1 stores unescaped plaintext password |
Previous Message | Thomas Hruska | 2014-05-16 04:42:27 | Re: BUG #10330: pg_ctl does not correctly honor "DETACHED_PROCESS" |