From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "girish R G peetle *EXTERN*" <giri(dot)anamika0(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: File System based PostgreSQL Database server restore to a different mount point. |
Date: | 2014-11-04 08:46:55 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B17D8BCEC@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
girish R G peetle wrote:
> We have requirement to perform File system based restore of entire PostgreSQL database server to a
> different mount point.
>
> -> I know that if no user created tablespaces are involved, we have just need to restore the entire
> DATA directory to new mount point, modify configuration parameters if required and then start the
> server.
> -> If user created table-space directories are involved, then we will have to manually adjust the
> symbolic links (under pg_tblspc) to the new tablespace directory path and bring up the server.
>
> Adjusting symbolic links is a workaround ( hook! ), is there a any official documentation on how
> 'PostgreSQL server restore to a different mount point' can be achieved ?
That should work.
The only documentation is at
http://www.postgresql.org/docs/9.3/static/continuous-archiving.html#BACKUP-PITR-RECOVERY
which mentions tablespaces, but does not discuss your case directly.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | girish R G peetle | 2014-11-04 10:16:53 | Re: File System based PostgreSQL Database server restore to a different mount point. |
Previous Message | girish R G peetle | 2014-11-04 05:50:31 | File System based PostgreSQL Database server restore to a different mount point. |