Thread: Strange behavior

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/

"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