On Tuesday, November 13, 2012 at 14:30, Tom Lane wrote:
>Gavan Schneider writes:
>>Since "CREATE TABLESPACE" is a PostgreSQL extension I would
>>love to see the concept fully populated with statements along
>>the lines of:
>>MOUNT TABLESPACE <name> [AT <file system location>] (default
>>is prev. known location)
>>UNMOUNT TABLESPACE <name> [IF EXISTS] (data is preserved)
>
>That is quite unlikely to happen, unfortunately. For that to work,
>tablespaces would have to be ...
>
And I'm not holding my breath. :)
As I thought, and you have confirmed, there are many reasons why
implementing this proposal would be hard. While I still think
there are reasons to consider it, I'm way too ignorant to know
whether the cost/benefit could ever favour such a change.
>Hard to tell what's going wrong ... it should work, but I can't debug
>"no joy".
>
Agree. Part of the problem is I don't know the system well
enough to dig for relevant clues (still learning), and since I
didn't setup the core system in the first place there's extra difficulties.
Finally, while I expect the answer is no, I need to repeat this question:
Is there an extraction tool that could pull data directly from
the TABLESPACE files?
Many thanks,
Gavan Schneider