pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Strange behavior 2+ messages / 2 participants [nested] [flat]
* Strange behavior @ 2007-03-27 19:32 Alexander B. <burbello3000@yahoo.com.br> 2007-03-28 00:51 ` Re: Strange behavior Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Alexander B. @ 2007-03-27 19:32 UTC (permalink / raw) To: pgsql-admin Hi, some developers were using the database, and suddenly no one could connect. Just only some connections that was established before. As soon as I was advised, I noticed that no postgres process were present, just only connections and they could run queries normally. Like this: desenv:~# ps -ef |grep postgres postgres 28010 27886 0 15:28 ? 00:00:00 postgres: desenv fabrica 10.90.2.116(57749) idle in transaction postgres 28013 27886 0 15:29 ? 00:00:00 postgres: desenv fabrica 10.90.2.112(51326) idle postgres 28051 27886 0 15:33 ? 00:00:01 postgres: desenv fabrica 10.90.2.115(51671) idle in transaction postgres 28110 27886 0 15:36 ? 00:00:00 postgres: desenv teste 10.90.2.14(48903) idle in transaction postgres 28134 27886 0 15:36 ? 00:00:01 postgres: desenv fabrica 10.90.2.115(60894) idle in transaction Strange that no log about what happened, were written. When I tried to stop, no process message was returned. Then, I started postgres again, and everything come back to run. Is there some patch to apply? Is it normal? Using PostgreSQL 8.1.4 on x86_64-pc-linux-gnu, compiled by GCC cc (GCC) 3.3.5 (Debian 1:3.3.5-13) Thanks Alexander _______________________________________________________ Yahoo! Mail - Sempre a melhor opção para você! Experimente já e veja as novidades. http://br.yahoo.com/mailbeta/tudonovo/ ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Strange behavior 2007-03-27 19:32 Strange behavior Alexander B. <burbello3000@yahoo.com.br> @ 2007-03-28 00:51 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2007-03-28 00:51 UTC (permalink / raw) To: Alexander B. <burbello3000@yahoo.com.br>; +Cc: pgsql-admin "Alexander B." <burbello3000@yahoo.com.br> writes: > some developers were using the database, and suddenly no one could connect. Sounds like your postmaster process died. > Using PostgreSQL 8.1.4 on x86_64-pc-linux-gnu, compiled by GCC cc (GCC) > 3.3.5 (Debian 1:3.3.5-13) On Linux the most common reason for this has been that the kernel OOM killer decides to pick on the postmaster. Try to disable memory overcommit. It's rumored that having too little swap space may result in the OOM killer firing even when overcommit is off, too. regards, tom lane ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2007-03-28 00:51 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2007-03-27 19:32 Strange behavior Alexander B. <burbello3000@yahoo.com.br> 2007-03-28 00:51 ` Tom Lane <tgl@sss.pgh.pa.us>
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