From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Andrus <kobruleht2(at)hot(dot)ee>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: permission denied for large object 200936761 |
Date: | 2021-02-01 21:02:39 |
Message-ID: | d1c9a330-0833-42e3-f85b-a0ccc3915394@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/1/21 12:07 PM, Andrus wrote:
> Hi!
>>>
>>> >Large objects exist independent of those. The important part of the
>>> above is lomowner. Use that oid to find the role that owns the
>>> objects here:
>>>
>>> /select rolname from pg_roles where oid = 30152 ; //
>
>>> Not sure what the above is supposed to be doing?
>>
> I showed the user definition
>>>
>>> It havent created any large objects.
>>
>> What hasn't created large objects?
> I
>>
>>>
>>> How to use this information to fix the issue ?
>>
>> Do the pg_dump as user clusteradmin.
>
> This works. However I need to allow non-supoeruser to create backup
> also. How to do this ?
Short term grant the dump user permissions on the large objects.
Long term figure out what they are and if they are needed or not.
>
> Andrus.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2021-02-01 21:28:02 | Re: permission denied for large object 200936761 |
Previous Message | Laurenz Albe | 2021-02-01 20:53:37 | Re: permission denied for large object 200936761 |