( OOps, forgot to cc the list again in previous, quoting all message for context ). On Mon, May 11, 2015 at 3:14 PM, Daniel Begin <jfd553@xxxxxxxxxxx> wrote: > Makes sense considering the error message! Maybe an image backup would make the job... I do not know how they are, made in windows, but it should. Also, IIRC there were versions of the GNU unix common utilities ( cp, rm, mv, ln ) for windows which correctly worked with links, if you can get hold of a reaosnable windows tar a 'tar c | tar x' should do the trick too. Also, look at the copy command help, in linux I know cp -a ( for archive ) does normally the trick. Francisco Olarte. > -----Original Message----- > From: Francisco Olarte [mailto:folarte@xxxxxxxxxxxxxx] > Sent: May-11-15 08:55 > To: Daniel Begin > Subject: Re: Restarting DB after moving to another drive > > Hi Daniel. > > On Mon, May 11, 2015 at 2:38 PM, Daniel Begin <jfd553@xxxxxxxxxxx> wrote: >> I just get it back running with the old drive - was some Windows >> hidden behavior! >> However, does someone could tell me what went wrong with the procedure >> I used to move the DB? > > It's been more than a decade since I've used windows, but from my past experience I'll bet you did not copy the DB right ( you did not copy the symbolic links, IIRC windows normal tools did not cope with them too well, but that was on w2k, YMMV ). > > Francisco Olarte. > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
