Re: Errors after cloning OS to new disk under Hyper-V

2020-07-17 Thread Tom Lane
writes: > From: Rob Sargent >> Have you tried to REINDEX as suggested? > I cannot get access to psql. If there is a way to reindex without having to > login first, I do not know how to do that. The disaster recovery process that Rob is suggesting goes like this: * Shut down server, if it's

Re: Errors after cloning OS to new disk under Hyper-V

2020-07-17 Thread Pavel Stehule
so 18. 7. 2020 v 6:36 odesílatel napsal: > -Original Message- > From: Rob Sargent > Sent: Saturday, July 18, 2020 5:56 AM > To: pgsql-general@lists.postgresql.org > Subject: Re: Errors after cloning OS to new disk under Hyper-V > > > Have you tried to REINDEX as

RE: Errors after cloning OS to new disk under Hyper-V

2020-07-17 Thread ertan.kucukoglu
-Original Message- From: Rob Sargent Sent: Saturday, July 18, 2020 5:56 AM To: pgsql-general@lists.postgresql.org Subject: Re: Errors after cloning OS to new disk under Hyper-V > Have you tried to REINDEX as suggested? I cannot get access to psql. If there is a way to reindex with

Re: Errors after cloning OS to new disk under Hyper-V

2020-07-17 Thread Rob Sargent
On 7/17/20 8:51 PM, ertan.kucuko...@1nar.com.tr wrote: Hello, This is PostgreSQL v10.10 64Bit, running on Windows 10 64Bit. One user, by himself, without asking for help, cloned his OS from one disk to Hyper-V disk. Old disk was not accessed, OS was shutdown while he is doing the cloning.