Skip site navigation (1) Skip section navigation (2)

Re: BUG #2099: too many private dirs ?

From: Tom(dot)Zschockelt(at)flender(dot)com
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2099: too many private dirs ?
Date: 2005-12-09 07:33:33
Message-ID: OFDDF586EB.4728EDF2-ONC12570D2.00293A96-C12570D2.00298B2A@flender.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi,

I've found the following additional lines in postmaster.log

2005-12-08 15:42:02 ERROR:  too many private dirs demanded
2005-12-08 15:42:03 ERROR:  too many private dirs demanded
2005-12-08 15:42:04 PANIC:  too many private files demanded
2005-12-08 15:42:04 CONTEXT:  writing block 236 of relation 
1663/19946/20844
This application has requested the Runtime to terminate it in an unusual 
way.
Please contact the application's support team for more information.
2005-12-08 15:42:04 LOG:  background writer process (PID 5748) was 
terminated by signal 3
2005-12-08 15:42:04 LOG:  terminating any other active server processes
2005-12-08 15:42:04 WARNING:  terminating connection because of crash of 
another server process
2005-12-08 15:42:04 DETAIL:  The postmaster has commanded this server 
process to roll back the current transaction and exit, because another 
server process exited abnormally and possibly corrupted shared memory.
2005-12-08 15:42:04 HINT:  In a moment you should be able to reconnect to 
the database and repeat your command.

Hope this helps 

regards Tom







Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
08.12.2005 16:57

 
        An:     "Tom" <tom(dot)zschockelt(at)flender(dot)com>
        Kopie:  pgsql-bugs(at)postgresql(dot)org
        Thema:  Re: [BUGS] BUG #2099: too many private dirs ?


"Tom" <tom(dot)zschockelt(at)flender(dot)com> writes:
> we got the following error in our environment:

> 2005-12-08 13:43:04 ERROR:  too many private dirs demanded
> 2005-12-08 13:43:04 ERROR:  checkpoint request failed
> 2005-12-08 13:43:04 HINT:  Consult the server log for details.

I can see a possible mechanism for this, but it requires assuming that
there have been repeated prior failures in the bgwriter/checkpointer.
What else is in the postmaster log?

                                                 regards, tom lane




pgsql-bugs by date

Next:From: wangshjDate: 2005-12-09 08:04:37
Subject: BUG #2103: System column oid is not unique
Previous:From: wangshjDate: 2005-12-09 06:59:24
Subject: pgsql8.1: About COPY Command and system clomn oid

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group