Re: Further clarification in documentation: No deletion of unreferenced large objects - Mailing list pgsql-docs

From David G. Johnston
Subject Re: Further clarification in documentation: No deletion of unreferenced large objects
Date
Msg-id CAKFQuwapNqDgnLo+V3Hy6shsSqHhsGg-3pQ4Rhq42DqAv4dxmA@mail.gmail.com
Whole thread Raw
In response to Further clarification in documentation: No deletion of unreferenced large objects  (PG Doc comments form <noreply@postgresql.org>)
List pgsql-docs
On Mon, Jun 12, 2023 at 8:32 AM PG Doc comments form <noreply@postgresql.org> wrote:

You may be onto something, but:

Page: https://www.postgresql.org/docs/15/datatype-binary.html

This page isn't relevant to the discussion at hand as it doesn't have anything to do with large objects.  Whether it should would be a different complaint.


When deleting a row that references (contains) a large object, I think that
most users expect the DBMS to take care of the, now unreferenced, BLOB.

On what grounds?  To me this looks just like any other foreign key situation and removing FK rows does not impact the PK.  What would lead one to think large objects behave differently?

David J.

pgsql-docs by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: Further clarification in documentation: No deletion of unreferenced large objects
Next
From: Laurenz Albe
Date:
Subject: Re: Further clarification in documentation: No deletion of unreferenced large objects