Thank you Dave,
I understand know, winxp sp2 allow all users to work on a predefined shared folder
for example this works fine:
CREATE TABLESPACE "tspgTest" LOCATION 'C:\\Documents and Settings\\All Users\\Documentos\\Databases';
for test purpouses only i assigned "postgres" user (in my case the user who starts PostgreSQL Database Server) to Administrators group but, then as you say, the service didn't start.
This is not postgres problem but i cannot find a place to assign "total control" or "write" access to user "postgres" to a specific folder. I don't remember if i can do it on windows xp sp1, but this means that all people that have win xp sp2 can create databases on default table spaces only; or can create tablespaces only on a shared folder (common place to all users who can write, delete, etc).
Later if i find something about this it i will post a message.
sorry if i don't write english well, but there is no other way to be up to date (actualizado).
Thanks
José
----- Original Message -----
Sent: Saturday, December 04, 2004 8:10 AM
Subject: Re: [pgadmin-support] Cannot Create a TableSpace on Windows XP Service Pack 2
Windows XP SP2 came with a lot of security patchs.
Something was changed on the way folders are managed, i don't know what.
Using pgAdmin III 1.2 RC2, when i want to create a Table Space with:
CREATE TABLESPACE "TestTS" LOCATION 'E:\\Proyecto2005\\Databases';
i have the following error:
ERROR: Could not set permissions on directory "E:/proyecto2005/Databases
User i currently has on WinXP belongs to administrators group, so i must not have problems creating folders or files anywhere.
Yesterday i've installed PostgreSQL 8 beta 5 without problems and i see two tablespaces pg_default and pg_global
Hi,
This is more of a PostgreSQL issue than pgAdmin, but, although the user you are running as has permission to create the required directory, it is not you that is actually doing it - the server is doing it on your behalf. Because the server runs under a user account without admin privileges (it won't even start with them), perhaps that user doesn't have the required rights?
So, the quick fix is to make sure your postgres user (or whatever you called it) has permission to write to the target directory.
Regards, Dave