| From: | justin <justin(at)emproshunts(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Roseller A(dot) Romanos" <don2_907(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Pls help |
| Date: | 2009-07-04 22:49:34 |
| Message-ID: | 4A4FDC7E.3010305@emproshunts.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe wrote:
> On Fri, Jul 3, 2009 at 10:02 PM, Roseller A. Romanos<don2_907(at)yahoo(dot)com> wrote:
>
> Note that this could be a permissions problem. All the files need to
> belong to whatever user postgres runs as.
>
>
If the destination PG install successfully started before there will be
no permission problems. When copying files from one computer to another
security credentials do not follow in Windows, security will be
inherited from parent directory by default.
The only time security in windows has that kind of problem is when
moving the physical hard drive to another computer. This creates
orphaned UUID describing security credentials in meta data of the NTFS
volume To clean up that kind of security mess requires first taking
ownership of the files then reseting all the permissions with replace
option.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | justin | 2009-07-04 22:58:08 | Re: Documentation - PgAdmin |
| Previous Message | Thomas Kellerer | 2009-07-04 21:03:06 | Will there be an official pg_migrator release? |