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:59:18 |
Message-ID: | 61aa8e4d-645a-31c8-53ba-c83a5e01e48e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/1/21 1:28 PM, Andrus wrote:
> Hi!
>
> >Long term figure out what they are and if they are needed or not.
>
> Non-superuser backup worked earlier. It looks like large objects
> suddenly appeared in database:
>
> select * from pg_largeobject_metadata
>
> Oid Lomowner
>
> 200936761 30152
> 200936762 30152
> 200936767 30152
>
> How to figure out what are large object with oids 200936761, 200936762
> and 200936767 ?
I misspoke earlier about large objects not being tied to a schema.table.
They can be as a column of type oid.
To see if they are try :
SELECT
relname,
attname
FROM
pg_attribute AS pa
JOIN pg_class AS pc ON pa.attrelid = pc.oid
WHERE
atttypid = 'oid'::regtype
AND relnamespace = 'public'::regnamespace
AND attnum > 0;
Where relnamespace is the schema you are interested in.
>
> Pd_dump throws error on first of them: 200936761
>
> Andrus.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2021-02-01 22:06:51 | Re: permission denied for large object 200936761 |
Previous Message | Andrus | 2021-02-01 21:28:02 | Re: permission denied for large object 200936761 |