Postgres Pro
Downloads
Home   >   mailing lists

Re: - Mailing list pgsql-general

From Kalai R
Subject Re:
Date
Msg-id CAGxuanMvME0TX+hJAAbj2FN8=0-4TQs_6UQqRmZsxUioco0_Ug@mail.gmail.com
Whole thread Raw
In response to Re:  (John R Pierce <pierce@hogranch.com>)
Responses Re:  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
Tree view
why not use the installer, which sets it all up correctly for you?

In previous, I use installer. but I face more data corruption problem and also server starting problem  when shutting down the system.  so I try to install my self. 


I think the problem is, you ran initdb as your user account, but the system service is running as the special system accounbt NETWORK_SERVICE, or similar, and there may be files in the data directory which the NETWORK_SERVICE account doesn't have write access writes to.   you can probably fix this with the cacls command.

I think you are correct. But I want to know why database corrupted even though I shutting down the machine properly. This is frequently happen when I use installer also.




On Wed, Jul 23, 2014 at 11:55 AM, John R Pierce <pierce@hogranch.com> wrote:
On 7/22/2014 11:14 PM, Kalai R wrote:
Well the above would indicate it is not being shutdown properly.

How are you shutting it down?

PSQL server starterd as stoped by postgresql windows service. So when I shutdown the machine postgres shutting down by postgres windows service

What and how are you installing?

Using windows binary zip file, I extract zip file and create cluster using intidb then register windows service using pg_ctl

Who are you running the service as?

I try to start the psql server from command prompt using pg_ctl.exe

why not use the installer, which sets it all up correctly for you?

I think the problem is, you ran initdb as your user account, but the system service is running as the special system accounbt NETWORK_SERVICE, or similar, and there may be files in the data directory which the NETWORK_SERVICE account doesn't have write access writes to.   you can probably fix this with the cacls command.





-- 
john r pierce                                      37N 122W
somewhere on the middle of the left coast

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re:
Next
From: John R Pierce
Date:
Subject: Re: