From: | Chander Ganesan <chander(at)otg-nc(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Omitting tablespace creation from pg_dumpall... |
Date: | 2006-06-16 03:13:23 |
Message-ID: | 449221D3.40609@otg-nc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
I'd like to suggest that a feature be added to pg_dumpall to remove
tablespace definitions/creation from the output. While the inclusion is
important for backups - it's equally painful when attempting to migrate
data from a development to production database. Since PostgreSQL won't
create the directory that will contain the tablespace, the tablespace
creation will fail. Following that, any objects that are to be created
in that tablespace will fail (since the tablespace doesn't exist).
This means that one could potentially have to search and replace every
instance of a tablespace name in a dump file...
Perhaps a flag can be added to simply comment out tablespace definitions
(both the creation, and their use in CREATE DATABASE, etc. statements).
This would allow the statement to be uncommented if needed, and allow
DBA's to search for and modify tablespace names as needed...
I apologize if this has already been mentioned/suggested :-)
--
Chander Ganesan
The Open Technology Group
One Copley Parkway, Suite 210
Morrisville, NC 27560
Phone: 877-258-8987/919-463-0999
http://www.otg-nc.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-16 03:33:17 | Re: Forcing backslash to be treated as ordinary string character |
Previous Message | Jim Nasby | 2006-06-15 20:24:10 | Re: VACUUMing sometimes increasing database size / sometimes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-06-16 03:14:06 | Re: Test request for Stats collector performance improvement |
Previous Message | Tom Lane | 2006-06-16 01:56:34 | Re: Test request for Stats collector performance improvement |