The following bug has been logged online:
Bug reference: 3232
Logged by: Carsten
Email address: fcarsten@tpg.com.au
PostgreSQL version: 8.2.3
Operating system: Windows XP SP 2
Description: Regression: pgsql server startup problem with encrypted
partitions
Details:
I am running the following scenario:
* Windows XP SP 2
* Postgres 8.2.3 installed on a normal Windows partition
* One highly sensitive database on a seperate table space which is located
on a TureCrypt partition
* The TrueCrypt partition only can be mounted after I log into the machine
(as I have to enter the password)
In the version of PostgreSQL which I was using previously (don't remember
version number) this scenario worked fine. As long as I didn't try to access
a database on the encrypted partition before mounting it the pgsql server
was happy.
In current version this no longer works. I have to manually restart the
pgsql server after mounting the encyprted partition to access the database
on it.
Were there any changes which made the pgsql server stricter in requiring
that all table-spaces exist on start-up? If yes, any chance of reversing
this to support databases on encrypted partitions or removable devices?
