Re: Schema authorization after create database.

From: Tsirkin Evgeny <tsurkin(at)mail(dot)jct(dot)ac(dot)il>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ian FREISLICH <if(at)hetzner(dot)co(dot)za>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Schema authorization after create database.
Date: 2004-08-12 11:04:58
Message-ID: 411B4EDA.1080308@mail.jct.ac.il
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Yep.But this is a little strange ,maybe we should ask to change it?
Evgeny.
Tom Lane wrote:
> Ian FREISLICH <if(at)hetzner(dot)co(dot)za> writes:
>
>>I ran into this little astonishment yesterday on 7.4.8. When I
>>create a database connected as the super user using:
>
>
>>CREATE DATABASE foo OWNER = foo;
>
>
>>The database is indeed owned by user foo, but the automatically
>>created public schema is is owned by the database super user. Should
>>this schema not be created as owned by the database owner specified
>>in the CREATE DATABASE command?
>
>
> That's the way it's supposed to work. CREATE DATABASE does not change
> anything inside the copied database.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message MPaule Torre 2004-08-12 12:51:28 redhat Ent3 et postegresql v7.4.3
Previous Message LISTMAN 2004-08-12 10:49:36 Re: [HACKERS] Where does the xlateSqlType symbol point