Discourse version: 2.5.0.beta4 ( e81a4048e3 ) When trying to backup, I get the error given below. [2020-05-16 10:09:19] pg_dump: processing data for table "public.reviewable_claimed_topics" [2020-05-16 10:09:19] pg_dump: dumping contents of table "public.reviewable_claimed_topics" [2020-05-16 10:09:…

TRUNCATE works, thanks. :smile:. I will now check if the backup is successful. EDIT: Oh no :frowning: ! [2020-05-17 16:56:39] pg_dump: Dumping the contents of table "post_search_data" failed: PQgetResult() failed. [2020-05-17 16:56:39] pg_dump: Error message from server: ERROR: invalid page in b…

Looks like a corrupt database to me based on the error message?

Is there any way to repair this database without losing data? I have the last backup 2 months ago and I don’t want to lose the created topics.

[图片] RikoDEV: public.scheduler_stats You got lucky that this table contains just sidekiq stats and nothing really important. You can try to remove this table rows and then try to trigger another backup. Hope only this table was affected :crossed_fingers:

The problem is that postgresql crashes when I try to clean this table. discourse=# DELETE FROM scheduler_stats; PANIC: corrupted item pointer: 10992 server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request…

Oh noes. Does a TRUNCATE on this table also fails?

备份过程中损坏的项目指针

支持安装

Falco (Falco) 2020 年5 月 17 日 16:25 4

你很幸运，这张表只包含 Sidekiq 的统计信息，没有其他真正重要的数据。你可以尝试删除这张表的行，然后再次触发备份。希望只有这张表受到了影响

话题		回复	浏览量
Repairing damaged post_search_data (unable to create database dumps and execute search reindex) Self-hosting	11	2709	2017 年2 月 13 日
Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) Self-hosting	12	4951	2020 年1 月 6 日
Backup failed due to PG/SQL errors Self-hosting	9	2532	2020 年12 月 17 日
Unable to backup with error on email_logs table Self-hosting	0	572	2023 年1 月 22 日
Can't restore saved backup Self-hosting	3	1326	2017 年3 月 7 日

备份过程中损坏的项目指针

相关话题