bruce wrote:
> Tom Lane wrote:
> > Bruce Momjian <br...@momjian.us> writes:
> > > Tom Lane wrote:
> > >> (Come to think of it, --link can fail on Unix too, if the user tries to
> > >> put the new database on a different filesystem. Have you got guards in
> > >> there to make sure this is discovered before the point of no return?)
> >
> > > Of course:
> > > ...
> > > though you have to delete the new cluster directory and remove the _old
> > > suffixes to get your old cluster back.
> >
> > That wasn't what I had in mind by "before the point of no return".
> > You should be making some effort to detect obvious failure cases
> > *before* the user has to do a lot of error-prone manual cleanup.
>
> That is something I will address during beta as I get problem reports.
I have implemented your suggestion:
Stopping postmaster servicing old cluster ok
Starting postmaster to service new cluster
waiting for postmaster to start ok
Stopping postmaster servicing new cluster ok
Could not create hard link between old and new data directories:
Cross-device link
In link mode the old and new data directories must be on the same file
system volume.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
