From: | "Medora Schauer" <mschauer(at)fairfield(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: fatal error in pg.log |
Date: | 2005-12-01 17:18:14 |
Message-ID: | 1CA058827877644DAB54FB930FFA3B0526AD41@lincoln.FAIRIND.FAIRFIELD.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> "Medora Schauer" <mschauer(at)fairfield(dot)com> writes:
> > I looked in the log again and sure enough I missed this immediately
> > before the WARNINGS:
>
> > PANIC: link from /data/database/pg_xlog/00000001000000D9 to
> > /data/database/pg_xlog/00000001000000E1 (initialization of log file
1,
> > segment 225) failed: No such file or directory
>
> > Looks like a file system problem right?
>
> Definitely seems like a can't-happen case. What file system are you
> running Postgres on?
I found this in /var/log/messages:
Dec 1 09:23:40 Qc kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
Dec 1 09:23:40 Qc kernel: VM: killing process postmaster
Is this because we are running out of memory?
Our file system is ext3.
Medora
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-12-01 17:25:22 | Re: 8.1, OID's and plpgsql |
Previous Message | marcelo Cortez | 2005-12-01 17:15:01 | Re: encoding problem |