| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Alexander B(dot)" <burbello3000(at)yahoo(dot)com(dot)br> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Strange behavior |
| Date: | 2007-03-28 00:51:47 |
| Message-ID: | 12360.1175043107@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Alexander B." <burbello3000(at)yahoo(dot)com(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phillip Smith | 2007-03-28 03:08:25 | Re: set password doesn't work |
| Previous Message | Simon Riggs | 2007-03-27 20:24:10 | Re: Priorities for users or queries? |