Re: [GENERAL] fatal error in pg.log

2005-12-01 Thread Martijn van Oosterhout
On Thu, Dec 01, 2005 at 11:18:14AM -0600, Medora Schauer wrote: > 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

Re: [GENERAL] fatal error in pg.log

2005-12-01 Thread Medora Schauer
> > "Medora Schauer" <[EMAIL PROTECTED]> writes: > > I looked in the log again and sure enough I missed this immediately > > before the WARNINGS: > > > PANIC: link from /data/database/pg_xlog/000100D9 to > > /data/database/pg_xlog/000100E1 (initialization of log file 1, > > segme

Re: [GENERAL] fatal error in pg.log

2005-12-01 Thread Tom Lane
"Medora Schauer" <[EMAIL PROTECTED]> writes: > I looked in the log again and sure enough I missed this immediately > before the WARNINGS: > PANIC: link from /data/database/pg_xlog/000100D9 to > /data/database/pg_xlog/000100E1 (initialization of log file 1, > segment 225) failed: N

Re: [GENERAL] fatal error in pg.log

2005-12-01 Thread Medora Schauer
I looked in the log again and sure enough I missed this immediately before the WARNINGS: PANIC: link from /data/database/pg_xlog/000100D9 to /data/database/pg_xlog/000100E1 (initialization of log file 1, segment 225) failed: No such file or directory LOG: server process (pid 574

Re: [GENERAL] fatal error in pg.log

2005-12-01 Thread Tom Lane
"Medora Schauer" <[EMAIL PROTECTED]> writes: > We are using ver 7.3.4 (old I know but we can't upgrade until early next > year) on a linux 2.4 system and are having some flaky problems with our > apps. They just die at apparently random times. In trying to figure > out what is going on I noticed

[GENERAL] fatal error in pg.log

2005-12-01 Thread Medora Schauer
We are using ver 7.3.4 (old I know but we can’t upgrade until early next year) on a linux 2.4 system and are having some flaky problems with our apps.  They just die at apparently random times.  In trying to figure out what is going on I noticed a couple of messages in pg.log that concern m