Re: Rights in 7.4

From: Francisco Reyes <lists(at)natserv(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql General List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Rights in 7.4
Date: 2004-01-14 16:52:32
Message-ID: 20040114164922.I11869@zoraida.natserv.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 14 Jan 2004, Tom Lane wrote:

> Francisco Reyes <lists(at)natserv(dot)com> writes:
> > Should restores be always done by the super user?
>
> If every object in the dump is owned by the same nonprivileged user,
> it will work to restore as that user.

They should all be owned by the user. I did the restore to the source DB
with that user.

> You can also use --no-owner to get the same effect

That didn't help.
Before I wrote to the list I searched archived and tried the following
line options:
--no-privileges --no-owner --no-reconnect

> Now that I think about it, the standard dump sequence will attempt to
> set permissions and comment on the public schema, which will fail if
> you're not superuser. But it should be okay to ignore those errors.

Before I tried the options above it also complained about an error to the
public schema, but that did not happen with the options above, however it
still had problems trying to set one sequence. I ended up doing that one
sequence with the superuser. Perhaps somehow I created that one sequence
with the superuser, but shouldn't the options above fix that case?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2004-01-14 17:03:51 Re: Collate is not supported for 7.4
Previous Message Edwin Quijada 2004-01-14 16:36:52 Recuperation Failed!!!!!