On Sun, Mar 15, 2020 at 07:23:49PM +0100, Karsten Hilbert wrote: > We then tried to DELETE the offending row > > delete from blobs.doc_obj where pk = 82224; > > but that, again, shows the "unexpected chunk" problem. According to http://www.databasesoup.com/2013/10/de-corrupting-toast-tables.html an UPDATE of the row is recommended -- should that work better than a DELETE ? I can't find documentation pointing to a fundamental implementation difference that suggests so. Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
