Re: permission denied for large object 200936761

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Andrus <kobruleht2(at)hot(dot)ee>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: permission denied for large object 200936761
Date: 2021-02-01 20:53:37
Message-ID: ed44153c97970e36d7f4266370fcb1d5110f2d91.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 2021-02-01 at 18:32 +0200, Andrus wrote:
> > > Database does not contain large objects.
> > >
> > > pg_dump starts to throw error
> > >
> > > ERROR: permission denied for large object 200936761
> >
> > Did you do the pg_dump as a superuser?
>
> No.
>
> pg_dump needs to be invoked by non-superuser also. It backs up two schemas, public and firma74 .

Obviously large objects *are* used.

You have to grant the database use permissions with

GRANT SELECT ON LARGE OBJECT 200936761 TO dumpuser;

Alternatively, use the -B option of pg_dump to skip dumping
large objects.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2021-02-01 21:02:39 Re: permission denied for large object 200936761
Previous Message Tom Lane 2021-02-01 20:40:27 Re: Segmentation fault on startup