Re: permission denied for large object 200936761

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Andrus <kobruleht2(at)hot(dot)ee>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)postgresql(dot)org
Subject: Re: permission denied for large object 200936761
Date: 2021-02-01 22:28:26
Message-ID: cb692fa2-80f6-d769-a260-9676f0d236ae@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/1/21 2:20 PM, Andrus wrote:
> Hi!
>
> >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.
>
> I added -B option and changed postgresql.conf  to
> lo_compat_privileges=on   as temporary fix.
>
> dumpuser has created backups of same two schemas for years without
> issues. The issue starts to occur today.

What code changed between the last backup and today?

>
> Application does not create large objects. It uses bytea columns instead.
>
> How to figure out what is this large object ?

You could try some of the functions here:

https://www.postgresql.org/docs/12/lo-funcs.html

to see if you can figure it out.
>
> Andrus.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2021-02-01 23:07:42 Re: permission denied for large object 200936761
Previous Message Andrus 2021-02-01 22:20:45 Re: permission denied for large object 200936761