Tom Lane wrote:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > I guess the issue is that I'd expect public to be owned by the DB Owner
> > after
> > a CREATE DATABASE foo OWNER bar,
>
> Why? Do you expect the system catalogs to be owned by the DB owner?
> What about other random objects that m
Alvaro Herrera wrote:
> Larry Rosenman wrote:
> > Greetings,
> > I think I found a bug, or at least a POLA violation. At work, I created
> > a user that is NOT a superuser, nor can that user create databases. When I
> > did a create database foo owner bar, all the schemas are set to be owned
Larry Rosenman <[EMAIL PROTECTED]> writes:
> I guess the issue is that I'd expect public to be owned by the DB Owner after
> a CREATE DATABASE foo OWNER bar,
Why? Do you expect the system catalogs to be owned by the DB owner?
What about other random objects that might have been created in the
tem
On Mon, 16 Apr 2007, Tom Lane wrote:
Larry Rosenman <[EMAIL PROTECTED]> writes:
When I try and RESTORE a pg_dump in the current state, we get errors because
the public schema is owned by postgres, and the grant commands are issued
as the user (since I'm restoring as the purported owner.
That'
Larry Rosenman <[EMAIL PROTECTED]> writes:
> When I try and RESTORE a pg_dump in the current state, we get errors because
> the public schema is owned by postgres, and the grant commands are issued
> as the user (since I'm restoring as the purported owner.
That's a different issue entirely, which
"Larry Rosenman" <[EMAIL PROTECTED]> writes:
> Shouldn't everything that is in the DB be owned by the purported owner?
Not any more than the owner of a schema owns everything in it.
regards, tom lane
---(end of broadcast)---
Andrew Dunstan wrote:
> Alvaro Herrera wrote:
> >Larry Rosenman wrote:
> >
> >>Greetings,
> >>I think I found a bug, or at least a POLA violation. At work, I
> >>created
> >>a user that is NOT a superuser, nor can that user create databases. When
> >>I
> >>did a create database foo ow
Alvaro Herrera wrote:
Larry Rosenman wrote:
Greetings,
I think I found a bug, or at least a POLA violation. At work, I created
a user that is NOT a superuser, nor can that user create databases. When I
did a create database foo owner bar, all the schemas are set to be owned by
the super
Larry Rosenman wrote:
> Greetings,
> I think I found a bug, or at least a POLA violation. At work, I created
> a user that is NOT a superuser, nor can that user create databases. When I
> did a create database foo owner bar, all the schemas are set to be owned by
> the superuser that created
On Mon, 16 Apr 2007, Andrew Dunstan wrote:
Larry Rosenman wrote:
Greetings,
I think I found a bug, or at least a POLA violation. At work, I
created
a user that is NOT a superuser, nor can that user create databases. When I
did a create database foo owner bar, all the schemas are set to
Larry Rosenman wrote:
Greetings,
I think I found a bug, or at least a POLA violation. At work, I created
a user that is NOT a superuser, nor can that user create databases. When I
did a create database foo owner bar, all the schemas are set to be owned by
the superuser that created the data
Greetings,
I think I found a bug, or at least a POLA violation. At work, I created
a user that is NOT a superuser, nor can that user create databases. When I
did a create database foo owner bar, all the schemas are set to be owned by
the superuser that created the database, not the database o
12 matches
Mail list logo
