| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Sergey Samokhin <prikrutil(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to simulate crashes of PostgreSQL? |
| Date: | 2009-08-24 06:56:25 |
| Message-ID: | dcc563d10908232356j5b71b8d5u35d042493398e956@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 24, 2009 at 12:49 AM, Craig
Ringer<craig(at)postnewspapers(dot)com(dot)au> wrote:
> You should also test your client's response to the Pg server remaining
> up but becoming non-responsive (eg: failed disk array causes Pg backends
> to remain in uninterruptable disk I/O system calls in the kernel). A
> possibly good way to do this is to SIGSTOP the backend(s).
This is a far more common and likely problem than the server crash
scenario. I've had servers go unresponsive under load before. Took
the load away and they came back, but the way the app responded has
not always been optimal. Many apps get jammed up from something like
this and require the app servers to be restarted.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2009-08-24 07:04:01 | Re: Install from Source On Windows - University of Sydney Research |
| Previous Message | Kushal Vaghani | 2009-08-24 06:54:19 | Re: Install from Source On Windows - University of Sydney Research |