On Thu, 2005-05-12 at 16:15 -0400, Tom Lane wrote:
> "Madeleine Theile" <[EMAIL PROTECTED]> writes:
> > But what if he doesn't? Then the only possibility is to drop all the
> > views and recreate them as another user in order to fix the issue with
> > the acl rights.
>
> See ALTER OWNER. The inte
"Madeleine Theile" <[EMAIL PROTECTED]> writes:
> But what if he doesn't? Then the only possibility is to drop all the
> views and recreate them as another user in order to fix the issue with
> the acl rights.
See ALTER OWNER. The intention is to make you give away all the owned
objects before get
On Wed, 2005-05-11 at 12:04 -0400, Tom Lane wrote:
> "Madeleine Theile" <[EMAIL PROTECTED]> writes:
> > After I've dropped one of the superusers that created and thus
> > owns some of the views and reinstalled it again with a different usesysid
>
> So reinstall it with the same usesysid --- that's
"Madeleine Theile" <[EMAIL PROTECTED]> writes:
> After I've dropped one of the superusers that created and thus
> owns some of the views and reinstalled it again with a different usesysid
So reinstall it with the same usesysid --- that's why the option exists
to specify sysid in CREATE USER.
Ther
Madeleine Theile wrote:
> Hi,
>
> first of all:
> I use Postgres-version: 7.3.9 and uname -a gives:
> Linux 2.4.21-286-smp4G
>
> Now here's the problem:
> I have several superusers in my database and some normal users that only
> have access to the data by views.
>
> After I've dropped one of th
Hi,
first of all:
I use Postgres-version: 7.3.9 and uname -a gives:
Linux 2.4.21-286-smp4G
Now here's the problem:
I have several superusers in my database and some normal users that only
have access to the data by views.
After I've dropped one of the superusers that created and thus
owns some o
