| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Turner <armtuk(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org, Alex Turner <aturner(at)neteconomist(dot)com> |
| Subject: | Re: IO Timeout |
| Date: | 2005-03-11 00:04:29 |
| Message-ID: | 27055.1110499469@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
Alex Turner <armtuk(at)gmail(dot)com> writes:
> I have a question about IO timeouts:
> We are using the 3ware escalade 9500S series of cards, and we had a
> drive failure this morning. Apparnetly the card waits 30 seconds for
> the drive to respond, and if it doesn't, it put's the drive in a fail
> state. Postgres it seems didn't wait 30 seconds before it decided
> that the system was upset, and put the database in maintainence mode.
> Is there a way to increase to IO wait timeout so this doesn't happen?
Postgres hasn't got any "IO timeouts". Your concern would be better
directed to whatever kernel you're using; any sort of timeout on a disk
operation would be happening at the kernel level.
For that matter, Postgres hasn't got any concept of "putting the
database in maintainence mode", so you haven't described what happened
very accurately at all.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-11 00:06:49 | Re: index creation in maintenance_work_mem or work_mem |
| Previous Message | Alex Turner | 2005-03-10 21:44:53 | Fwd: IO Timeout |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoffrey | 2005-03-11 00:09:34 | Re: PostgreSQL still for Linux only? |
| Previous Message | Tom Lane | 2005-03-10 23:46:13 | Re: the impact of encoding on performance. |