Tom Lane wrote:
With PostgreSQL 8.1.4, if I do the following:Chander Ganesan <[EMAIL PROTECTED]> writes: create tablespace test location '/srv/tblspc'; create database test with tablespace = test; The pg_dumpall result will contain: CREATE TABLESPACE test OWNER postgres LOCATION '/srv/tblspc'; CREATE DATABASE test WITH TEMPLATE=template0 OWNER=postgres ENCODING='utf8' TABLESPACE=test; When this is executed on a load, the create database statement will fail with a 'ERROR: tablespace test does not exist'. This error occurs due to the fact that the initial create tablespace statement fails...because the location isn't pre-created. Perhaps the feature you mention (SET default_tablespace) is a feature that is to be added post PostgreSQL 8.1 ? The set default_tablespace method definitely sounds like the ideal solution here...although its potentially misleading if a DBA doesn't realize that the tablespace wasn't actually created... Subsequent create statements inside the database will fail, since the database create will fail. -- 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 regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |
- [GENERAL] Omitting tablespace creation from pg_dumpall... Chander Ganesan
- Re: [GENERAL] Omitting tablespace creation from pg_d... Tom Lane
- Re: [GENERAL] Omitting tablespace creation from ... Chander Ganesan
- Re: [GENERAL] Omitting tablespace creation f... Florian G. Pflug
- Re: [GENERAL] Omitting tablespace creati... Bruce Momjian
- Re: [GENERAL] Omitting tablespace creati... Chander Ganesan
