| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Vick Khera <vivek(at)khera(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to simulate crashes of PostgreSQL? |
| Date: | 2009-08-25 17:09:34 |
| Message-ID: | 20090825170934.GB12604@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Vick Khera wrote:
> On Sat, Aug 22, 2009 at 6:55 PM, Greg Sabino Mullane<greg(at)turnstep(dot)com> wrote:
> > A server crash is a pretty rare event in the Postgres world, so I
> > would not spend too many cycles on this...
>
> I had one the other day caused by server resource issues: I ran out of
> file descriptors when I had a very large surge in activity. Pg
> rightfully panicked and disconnected all my clients.
PG is not supposed to crash when it runs out of file descriptors. In
fact there's a whole abstraction layer to ensure this does not happen.
What you saw was either misconfiguration or a bug somewhere (for example
maybe you have untrusted functions that try to open files?)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Brown | 2009-08-25 17:12:05 | PL/pgSQL infinite loop in "UPDATE/INSERT" example |
| Previous Message | Tom Lane | 2009-08-25 17:05:06 | Re: Invalid memory alloc request |