To me that looks like an issue with the associated TOAST table. I do not have a suggestion at this time. Maybe this rings a bell with someone else. -- Adrian Klaver adrian.klaver@aklaver.com
Good tip, x method, I will try it, sure.
But I'm also afraid that there is a still hidden issue.
I think that I'm using postgres in a context slightly different from the usual ones (many many updates of a table rows with big field, replication,...) so I'm afraid that issues not already seen can appear.
