Re: Further clarification in documentation: No deletion of unreferenced large objects

2023-06-14 Thread Laurenz Albe
On Tue, 2023-06-13 at 10:57 +, Oliver Marienfeld wrote: > I would understand if you decided against extending the docs. I don't get to decide that. If you come up with a patch for the documentation, that would increase the chances that the documentation actually gets changed. Yours, Laurenz

Re: Further clarification in documentation: No deletion of unreferenced large objects

2023-06-13 Thread Oliver Marienfeld
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. Thanks for pointing this out. I picked the wrong page. When deleting a row that references (contains) a large object, I think that most us

Re: Further clarification in documentation: No deletion of unreferenced large objects

2023-06-12 Thread Laurenz Albe
On Mon, 2023-06-12 at 13:48 +, 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 kn

Re: Further clarification in documentation: No deletion of unreferenced large objects

2023-06-12 Thread David G. Johnston
On Mon, Jun 12, 2023 at 8:32 AM PG Doc comments form 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 d

Re: Further clarification in documentation: No deletion of unreferenced large objects

2023-06-12 Thread Erik Wienhold
> On 12/06/2023 15:48 CEST PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/datatype-binary.html > Description: > > When deleting a row that references (contains) a large object, I think that > most use