This makes the most sense.  By default, horde should own the database 
- the admin can always change this if they don't agree.  Added to 
3.3.4 and HEAD.

Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/horde/scripts/sql/create.pgsql.sql?rt=horde&r1=1.1.10.22&r2=1.1.10.23&ty=u

Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/horde/scripts/sql/create.pgsql.sql?rt=horde&r1=1.35&r2=1.36&ty=u

Ok, the default access privileges for public users are configured 
differently on our systems. The part "=UC/postgres" means public users 
can Use (i.e., select) and Create on the public schema (and these 
privileges have been granted by the user postgres). I've removed 
create privileges for public users in my database. That's why it's 
working for you and not for me.



By default, Postgres allows any account to login to any database and 
create objects on the public schema. I suppose it's possible someone 
may have gone a step further and configured their template database to 
prevent public users from logging in at all.



I imagine a foolproof version of the script would look something like this:



CREATE USER horde;

  -- ALTER USER horde WITH PASSWORD 'pass';

CREATE DATABASE horde OWNER horde;

\c horde horde;



Alternatively, if you don't want horde to own the database (I don't 
know the security implications one way or the other):



CREATE DATABASE horde;

CREATE USER horde;

  -- ALTER USER horde WITH PASSWORD 'pass';

GRANT CONNECT ON DATABASE horde TO horde;

\c horde

GRANT CREATE ON SCHEMA public TO horde;

SET ROLE horde;



I haven't test any of this, so you may want to play around and see 
how/if this works.

         Name        |  Owner   |          Access privileges           
|           Description

--------------------+----------+-------------------------------------+----------------------------------

  information_schema | postgres | {postgres=UC/postgres,=U/postgres}  |

  pg_catalog         | postgres | {postgres=UC/postgres,=U/postgres}   
| system catalog schema

  pg_toast           | postgres |                                     
| reserved schema for TOAST tables

  pg_toast_temp_1    | postgres |                                     |

  public             | postgres | {postgres=UC/postgres,=UC/postgres} 
| standard public schema

(5 rows)

I'm the original reporter of this bug. Please try running the command 
'\dn+' from your template1 database and post the output.

Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/horde/scripts/sql/create.pgsql.sql?rt=horde&r1=1.1.10.21&r2=1.1.10.22&ty=u

I have:

Welcome to psql 8.3.6 (server 8.3.5), the PostgreSQL interactive terminal.
I don't see this.  The script runs fine for me (although I'm not a 
postgres/SQL expert by any stretch of the imagination).
This makes sense.  I have added this part.

Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/horde/scripts/sql/create.pgsql.sql?rt=horde&r1=1.34&r2=1.35&ty=u

Can anybody running pg look into this?

Hi,



I forward you a bug reported by a Debian user 
(http://bugs.debian.org/508571) :



The create.pgsql.sql script fails (running postgresql 8.3.5). After 
creating and switching to the horde database, it fails to create new 
relations with error

"permission denied for schema public".



The script erroneously grants CREATE on the database, which only 
allows creation of new schemas:



GRANT CREATE on DATABASE horde to horde;

\c horde horde;





The script should grant CREATE on the schema:



\c horde

GRANT CREATE ON SCHEMA public TO horde;

SET ROLE horde;



Also, the script should probably run inside a transaction. After the 
script fails, the user is left the horde user and an empty horde 
database.