Re: pg_basebackup for streaming base backups
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-01-16T17:18:47Z
Lists: pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes: >> + * The file will be named base.tar[.gz] if it's for the main data directory >> + * or <tablespaceoid>.tar[.gz] if it's for another tablespace. >> >> Well we have UNIQUE, btree (spcname), so maybe we can use that here? > We could, but that would make it more likely to run into encoding > issues and such - do we restrict what can be in a tablespace name? No. Don't even think of going there --- we got rid of user-accessible names in the filesystem years ago and we're not going back. Consider CREATE TABLESPACE "/foo/bar" LOCATION '/foo/bar'; regards, tom lane