Re: Introduction of a new field in pg_class indicating presence of a large object in a table

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Gaurav Pant <gauravpant145(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Introduction of a new field in pg_class indicating presence of a large object in a table
Date: 2024-04-30 19:13:52
Message-ID: CAKFQuwY4xifDbf8EZKwYtrECQiCbYsK_RLo+vnnWN-MuSSaqLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 30, 2024 at 11:57 AM Gaurav Pant <gauravpant145(at)gmail(dot)com>
wrote:

> I wanted to know if there is any such system table that we can use to
> identify and map the fields containing large objects and the respective
> tables and if it is not already there, do we have any plans to incorporate
> the same in pg_class like we have for pg_toast?
>
>
https://www.postgresql.org/docs/current/catalog-pg-largeobject.html

Large Objects are nothing like TOAST. There is no system level association
between large objects and tables. Sure, the DBA can choose to store a
large object OID in a table, but how you'd go about figuring out which
columns contain those is going to be installation specific. Though
hopefully they used a bigint data type and maybe added "oid" to the column
name...I suppose it would be interesting if one could define a FK on a
table and point it at pg_largeobject_metadata but that I suspect would be
the extent to which we'd do something along the lines of your request.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2024-04-30 19:28:05 Re: Introduction of a new field in pg_class indicating presence of a large object in a table
Previous Message Gaurav Pant 2024-04-30 18:56:41 Introduction of a new field in pg_class indicating presence of a large object in a table