| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Paul Lambert <paul(dot)lambert(at)autoledgers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PG periodic Error on W2K |
| Date: | 2007-03-01 15:45:16 |
| Message-ID: | 24513.1172763916@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Mar 01, 2007 at 09:44:19AM +0900, Paul Lambert wrote:
>> I am periodically getting errors pop up on the server console of the
>> following nature:
>> The File or directory D:\PostgresQL\Data\global\pgstat.stat is corrupt
>> and unreadable. Please run the Chkdsk utility.
> They can *not* be caused by a bug in PostgreSQL - no more than a kernel
> oops in linux is the fault of PostgreSQL. Now, we do push the filesystem
> and disk layer in an unusual way with the pgstats writes, gievn that we
> rewrite the same file over and over and over and over again at very
> short intervals. But nothing says we're not allowed to do that :-)
I'm wondering whether the message is coming from the kernel, or some
sort of file-scanning utility that gets confused when a file is deleted
while it's looking at it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-03-01 15:51:33 | Re: PG periodic Error on W2K |
| Previous Message | Brian A. Seklecki | 2007-03-01 15:34:15 | Re: why can't I increase shared buffers to higher value? |