Please don't allow posting: Re: Restoring data from TABLESPACE files

Greetings

Still sorting out my anti-spam measures and the super private
address has leaked through to yourself, and Tom Lane... I'm sure
you can both be trusted but I'm not sure about the list. I have
already received soem UCE to pg-gts@snkmail.com, nothing too
horrible, but it certainly is not a private list.

Is it possible to suppress the message, and I simply repost later?

Regards, and thanks
Gavan


Received: from magus.postgresql.org ([87.238.57.229])
     by malur.postgresql.org with esmtp (Exim 4.72)
     (envelope-from <********************>)
     id 1TYV7o-0004N7-QG
     for pgsql-novice@postgresql.org; Wed, 14 Nov 2012 05:02:56 +0000
Received: from nschwmtas01p.mx.bigpond.com ([61.9.189.137])
     by magus.postgresql.org with esmtp (Exim 4.72)
     (envelope-from <********************>)
     id 1TYV7m-0004Or-DK
     for pgsql-novice@postgresql.org; Wed, 14 Nov 2012 05:02:55 +0000
Received: from nschwcmgw05p ([61.9.190.165]) by nschwmtas01p.mx.bigpond.com
           with ESMTP
           id <20121114050249.QZGA4662.nschwmtas01p.mx.bigpond.com@nschwcmgw05p>;
           Wed, 14 Nov 2012 05:02:49 +0000
Received: from pendari.net ([124.181.105.146])
     by nschwcmgw05p with BigPond Outbound
     id PH2l1k00L39YDhG01H2nTn; Wed, 14 Nov 2012 05:02:49 +0000
X-Authority-Analysis: v=2.0 cv=D4zF24tj c=1 sm=1
  a=CtujcZ5SGlGx4EGomLHF4w==:17 a=GBEPjh4lDs8A:10 a=BUl4cw8wsZUA:10
  a=IkcTkHD0fZMA:10 a=9BvCZD0AAAAA:8 a=m9o3UCVuAAAA:8 a=hnKv142_Qk4A:10
  a=oyyS19XRZzAh_TlDkMAA:9 a=QEXdDO2ut3YA:10 a=CtujcZ5SGlGx4EGomLHF4w==:117
Date: Wed, 14 Nov 2012 16:02:46 +1100
From: Gavan Schneider <********************>
Subject: Re: [NOVICE] Restoring data from TABLESPACE files
To: "Tom Lane tgl-at-sss.pgh.pa.us |pg-gts/Basic|" <b6ba5fbx3t@sneakemail.com>
cc: pgsql-novice@postgresql.org
X-Priority: 3
In-Reply-To: <7096.1352863816@sss.pgh.pa.us>
Message-ID: <r422Ps-1075i-EFB7965990E9416D9941B473B860A32D@pendari.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.3.1 (422)
X-Pg-Spam-Score: 0.4 (/)


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
--
Gavan Schneider             <gavan@galeel.org>
Ph. +61 2 6355 6256         "Pendari" Anarel Road
Mb. +61 405 124 883         Sodwalls NSW 2790
                             Australia