|
|||||||||||
|
[NOVICE] Access rights for tablespaces, phpPgAdmin versus PgAdmin
From: Kenneth Porter <shiva(at)sewingwitch.com>
Date: Wed Nov 14 2007 - 21:45:54 EST
I got postgres installed on CentOS 5 with yum, started the server (which creates the initial database), and installed phpPgAdmin on the same server under Apache. I then installed PgAdmin 1.8.0 on my XP box on my LAN. Using psql, I created a login role with all rights except superuser. I got my head around pg_hba.conf so I can log into both phpPgAdmin and PgAdmin from my XP system using my new role account. I then proceeded to create a new database in which to copy existing tables from another (Windows-based) application. (I plan to use the ODBC connector.) (As I type this, I just tried this with phpPgAdmin and it worked. I'll continue, though....) PgAdmin refuses to let me create the new DB, telling me "permission denied for tablespace pg_default". Some googling suggests that this is intentional, that if one wants to create a new table one needs to change the default tablespace permissions to allow it, or create a new tablespace. So why does phpPgAdmin succeed, and PgAdmin fail? What's the correct procedure to follow here? (I don't need a separate tablespace at this time, although I don't have a problem with creating one.) Do I need to change permissions on pg_default, and if so, how? I don't see where I can change permissions on a tablespace in PgAdmin.
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
Received on Wed Nov 14 21:48:42 2007This archive was generated by hypermail 2.1.8 : Thu Jun 19 2008 - 00:03:56 EDT |
||||||||||
|
|||||||||||