Re: managing tablespaces like files? - Mailing list pgsql-general

From Sam Carleton
Subject Re: managing tablespaces like files?
Date
Msg-id 8d38ca0a1003081548k26ad233bv8bf918861fa89db6@mail.gmail.com
Whole thread Raw
In response to Re: managing tablespaces like files?  (John R Pierce <pierce@hogranch.com>)
Responses Re: managing tablespaces like files?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, Mar 8, 2010 at 5:46 PM, John R Pierce <pierce@hogranch.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

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: managing tablespaces like files?
Next
From: Tom Lane
Date:
Subject: Re: managing tablespaces like files?