What does top report as using the most memory?

On Wed, May 23, 2007 at 11:01:24PM -0300, Leandro Guimar?es dos Santos wrote:
> Hi all,
> 
>  
> 
> I have a 4 CPU, 4GB Ram memory box running PostgreSql 8.2.3 under Win 2003 in 
> a very high IO intensive insert application.
> 
>  
> 
> The application inserts about 570 rows per minute or 9 rows per second.
> 
>  
> 
> We have been facing some memory problem that we cannot understand.
> 
>  
> 
> From time to time memory allocation goes high and even after we stop 
> postgresql service the memory continues allocated and if were restart the 
> service the Postgres crash over.
> 
>  
> 
> It's a 5 GB database size already that was born 1 and a half month ago. We 
> have 2 principal tables partitioned.
> 
>  
> 
> Above is the log file. Do anyone have any idea what could the problem be......
> 
>  
> 
> Thanks in advance.
> 
>  
> 
>  
> 
> 2007-05-23 13:21:00 LOG:  CreateProcess call failed: A blocking operation was 
> interrupted by a call to WSACancelBlockingCall.
> 
>              (error code 1450)
> 
> 2007-05-23 13:21:00 LOG:  could not fork new process for connection: A 
> blocking operation was interrupted by a call to WSACancelBlockingCall.
> 
>             
> 
> 2007-05-23 13:21:06 LOG:  could not receive data from client: An operation on 
> a socket could not be performed because the system lacked sufficient buffer 
> space or because a queue was full.
> 
> 2007-05-23 13:21:17 LOG:  server process (PID 256868) exited with exit code 
> 128
> 
> 2007-05-23 13:21:17 LOG:  terminating any other active server processes
> 
> 2007-05-23 13:21:17 WARNING:  terminating connection because of crash of 
> another server process
> 
> 2007-05-23 13:21:17 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.
> 
> 2007-05-23 13:21:17 HINT:  In a moment you should be able to reconnect to the 
> database and repeat your command.
> 
> 2007-05-23 13:21:17 WARNING:  terminating connection because of crash of 
> another server process
> 
> 2007-05-23 13:21:17 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.
> 
> 2007-05-23 13:21:17 WARNING:  terminating connection because of crash of 
> another server process
> 
> 2007-05-23 13:21:17 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.
> 
>  
> 

-- 
Jim Nasby                                      [EMAIL PROTECTED]
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

Attachment: pgp0D3edkaqiH.pgp
Description: PGP signature

Reply via email to