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
In response to
pgsql-hackers by date
|Next:||From: Greg Sabino Mullane||Date: 2008-04-02 12:55:40|
|Subject: Re: Friendly help for psql|
|Previous:||From: Dimitri Fontaine||Date: 2008-04-02 10:33:56|
|Subject: Re: GiST opclass and varlena|
pgsql-general by date
|Next:||From: Greg Sabino Mullane||Date: 2008-04-02 13:07:01|
|Subject: Re: [GENERAL] SHA1 on postgres 8.3|
|Previous:||From: Albe Laurenz||Date: 2008-04-02 12:18:25|
|Subject: Re: Foreign keys causing conflicts leading toserialization failures|