| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Morris Goldstein <morris(dot)x(dot)goldstein(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Can Postgres 8.x start if some disks containing tablespaces are not mounted? |
| Date: | 2008-04-02 12:44:08 |
| Message-ID: | 47F37F98.60005@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Morris Goldstein napsal(a):
> But that makes me wonder: what about this sequence of events:
>
> - Postgres running normally on /dev/sda and /dev/sdb.
> - Update to table in /dev/sdb tablespace is committed but still exists in WAL.
> - Postgres crashes (e.g. power failure).
> - Postgres starts with /dev/sda only.
> - Recovery needs to update table in /dev/sdb tablespace.
>
> I assume bad things will happen in this case.
yes, Probably best solution in this case is to implemented tablespace
availability into postgreSQL and PostgreSQL shouldn't start when tablespace is
missing.
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2008-04-02 13:07:01 | Re: [GENERAL] SHA1 on postgres 8.3 |
| Previous Message | Albe Laurenz | 2008-04-02 12:18:25 | Re: Foreign keys causing conflicts leading toserialization failures |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2008-04-02 12:55:40 | Re: Friendly help for psql |
| Previous Message | Dimitri Fontaine | 2008-04-02 10:33:56 | Re: GiST opclass and varlena |