| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Brandl, Wolfgang *EXTERN*'" <wolfgang(dot)brandl(at)brz(dot)gv(dot)at>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: postgres pg_basebackup |
| Date: | 2017-05-12 09:27:08 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B53A37793@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I wrote:
>> During an online backup, a file "tablespace_map" is created in the data directory that
>> contains the original locations of the tablespaces.
>>
>> During recovery, the symbolic links are restored from that directory.
>>
>> So you have to un-tar the tablespaces into the same location as in the original database
>> cluster. The good news is that you can find the locations in the "tablespace_map" file
>> and don't need to document them somewhere.
Wolfgang Brandl wrote:
> Thanks it is working perfectly.
> Even if i choose to redirect the database to new location and adapting the tablespace_map
> file to this new locations it is working.
> Do you think there are any concerns doing this redirect restore?
That should be fine.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-05-12 13:12:52 | Re: [SQL] exporting query result |
| Previous Message | Steven Chang | 2017-05-12 09:25:00 | Re: wal segment size |