| From: | Vivek Khera <vivek(at)khera(dot)org> |
|---|---|
| To: | "Pgsql-General(at)Postgresql(dot)Org general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgresql data integrity during RAID10 drive rebuild |
| Date: | 2006-11-29 18:24:25 |
| Message-ID: | 1E8348E8-FBF3-421D-864D-99D820E6EBC4@khera.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Nov 29, 2006, at 11:56 AM, Steve Poe wrote:
> I've never had to replace a disc in an array with Postgresql
> running on it. LSI says I can replace the disc and do a rebuild
> while everything is running. I am of course concerned about data
> integrity/corruption.
>
This is the whole entire complete purpose you have a RAID card and
hot-swap drives: To make it transparent to the layers above the disk
interface.
> Has anyone had to rebuild one of their disc in an array of their
> database?
Yes. The OS (let alone an application such as the DB) has no clue
other than possibly slower response from the mirrored pair being
rebuilt.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2006-11-29 18:41:09 | Re: coalesce with all nulls can only be assigned to |
| Previous Message | Tom Lane | 2006-11-29 18:15:40 | Re: coalesce with all nulls can only be assigned to text |