Re: pg_basebackup for streaming base backups - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_basebackup for streaming base backups
Date
Msg-id 9087.1295198327@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_basebackup for streaming base backups  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_basebackup for streaming base backups  (Magnus Hagander <magnus@hagander.net>)
List 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.  ConsiderCREATE TABLESPACE "/foo/bar" LOCATION '/foo/bar';
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: walreceiver fallback_application_name
Next
From: Simon Riggs
Date:
Subject: Re: We need to log aborted autovacuums