Re: pg_basebackup for streaming base backups

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup for streaming base backups
Date: 2011-01-16 17:18:47
Message-ID: 9087.1295198327@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2011-01-16 17:20:55 Re: pg_basebackup for streaming base backups
Previous Message Magnus Hagander 2011-01-16 17:18:28 Re: walreceiver fallback_application_name