From: | Sam Carleton <scarleton(at)miltonstreet(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: managing tablespaces like files? |
Date: | 2010-03-08 23:48:05 |
Message-ID: | 8d38ca0a1003081548k26ad233bv8bf918861fa89db6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 8, 2010 at 5:46 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>
>> I hear you, but I am not willing to throw in the towel, just yet...
>> Generally speaking, is there a lot of metadata that would need to be
>> exported? As I think about this, I am thinking I would have to read in ALL
>> the system tables and find all the different parts to make up all the
>> different aspects of all the stuff in the tablespace, like the tables,
>> columns, views, stored procs, etc. It isn't a matter of just dumping one or
>> two tables, but a matter of combing lots of tables and exporting lots of
>> very specific pieces of those tables. Correct?
>>
>
> how about...
> pg_dump -Fc dbname >filename.dump
>
One of the cases I need to be concerned with is the case where the
application is shut down, the user goes in and deletes the tablespace folder
by way of deleting the parent folder. How will PostgreSQL handle such a
situation?
Sam
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-03-09 00:59:25 | Re: managing tablespaces like files? |
Previous Message | Thomas Kellerer | 2010-03-08 23:00:53 | \copy command: how to define a tab character as the delimiter |