From: Laurenz Albe <laurenz.albe@cybertec.at>
To: oliver_schmidt_@hotmail.de
To: pgsql-docs@lists.postgresql.org
Subject: Re: Further clarification in documentation: No deletion of unreferenced large objects
Date: Mon, 12 Jun 2023 18:48:54 +0200
Message-ID: <5d0349511403954daf7578bdab2271a55ddb3395.camel@cybertec.at> (raw)
In-Reply-To: <168657770315.399156.14528203301769250174@wrigleys.postgresql.org>
References: <168657770315.399156.14528203301769250174@wrigleys.postgresql.org>
On Mon, 2023-06-12 at 13:48 +0000, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/15/datatype-binary.html
>
> 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. It's
> good to know that PostgreSQL handles this differently and that one must
> periodically use vacuumlo to avoid BLOB data piling up. At least, that's
> what I understood.
>
> I think a small paragraph in the documentation about this would help many
> people. I can help with writing, if needed.
This is documented here:
https://www.postgresql.org/docs/current/lo.html
Admittedly, that is not the best place. Perhaps the introductory chapter
in https://www.postgresql.org/docs/current/lo-intro.html would be a good
place to mention that there is no referential integrity to large objects.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, oliver_schmidt_@hotmail.de, pgsql-docs@lists.postgresql.org
Subject: Re: Further clarification in documentation: No deletion of unreferenced large objects
In-Reply-To: <5d0349511403954daf7578bdab2271a55ddb3395.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox