Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
От | Tom Lane |
---|---|
Тема | Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619 |
Дата | |
Msg-id | 198233.1643863841@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619 (Justin Pryzby <pryzby@telsasoft.com>) |
Список | pgsql-bugs |
Justin Pryzby <pryzby@telsasoft.com> writes: > On Thu, Jan 27, 2022 at 08:57:28PM +0000, PG Bug reporting form wrote: >> Issue: ERROR: missing chunk number 0 for toast value 152073604 in >> pg_toast_2619 >> we are facing issue with mentioned short description error while trying any >> operation on database. > From my notes from a handful of years ago, I think you'll have luck doing some > things like this: The good news is that that's the toast table for pg_statistic, which means that there is exactly no irreplaceable data in it. If all else fails, you can just truncate pg_statistic and then re-ANALYZE the whole database to rebuild it. (I say "just" truncate pg_statistic, but you'll have to do that in a standalone backend started with the -O option, else there are permissions checks that will prevent it.) The bad news is that there might be more corruption lurking elsewhere. What event precipitated this? I think we have seen some bugs that would preferentially affect pg_statistic, but not recently. If you're not running a current minor release, an update is advisable. regards, tom lane
В списке pgsql-bugs по дате отправления: