pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Memory allocation and Vacuum abends
2+ messages / 2 participants
[nested] [flat]

* Memory allocation and Vacuum abends
@ 2007-05-24 02:01  Leandro Guimarães dos Santos <lgsantos@contax.com.br>
  0 siblings, 1 reply; 2+ messages in thread

From: Leandro Guimarães dos Santos @ 2007-05-24 02:01 UTC (permalink / raw)
  To: pgsql-performance

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.

 

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Memory allocation and Vacuum abends
@ 2007-05-27 16:06  Jim C. Nasby <decibel@decibel.org>
  parent: Leandro Guimarães dos Santos <lgsantos@contax.com.br>
  0 siblings, 0 replies; 2+ messages in thread

From: Jim C. Nasby @ 2007-05-27 16:06 UTC (permalink / raw)
  To: Leandro Guimar?es dos Santos <lgsantos@contax.com.br>; +Cc: pgsql-performance

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                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2007-05-27 16:06 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-05-24 02:01 Memory allocation and Vacuum abends Leandro Guimarães dos Santos <lgsantos@contax.com.br>
2007-05-27 16:06 ` Jim C. Nasby <decibel@decibel.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox