On Mon, Dec 3, 2012 at 02:38:20AM -0000, Greg Sabino Mullane wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > > > As there isn't (as far as I know at least) any actual *point* in > > creating a tablespace inside the main data directory, should we > > perhaps disallow this in CREATE TABLESPACE? Or at least throw a > > WARNING if one does it? > > Sure there is a point - emulating some other system. Could be > replication, QA box, disaster recovery, etc. I'd be > cool with a warning, but do not think we should disallow it.
FYI, someone put their new cluster inside an existing old tablespace, and when they ran the script to delete their old install, their new install was deleted too. My answer was, "Don't do that". -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
