更新时间:2023-12-22 GMT+08:00

xlog

GS_113040326

错误码: syntax error in history file: %s.

解决方案:应为数字时间轴ID。

level: FATAL

GS_113040327

错误码: invalid data in history file: %s.

解决方案:时间轴ID必须是递增的顺序。

level: FATAL

GS_113040328

错误码: invalid data in history file %s.

解决方案:时间轴ID必须小于子时间轴的ID。

level: FATAL

GS_113040337

错误码: recovery command file %s specified neither primary_conninfo nor restore_command.

解决方案:数据库服务器将定期轮询pg_xlog子目录以检查放置在该位置的文件。

level: WARNING

GS_113120083

错误码: could not reset replication slot at the end of recovery.

解决方案:删除复制槽或增加max_replication_slots。

level: WARNING

GS_113120111

错误码: Could not locate required checkpoint record.

解决方案:如果不是从备份恢复,请尝试删除文件“%s backup_label”。

level: FATAL

GS_113120112

错误码: could not find redo location referenced by checkpoint record.

解决方案:如果不是从备份恢复,请尝试删除文件“%s backup_label”。

level: FATAL

GS_113120168

错误码: invalid replication slot recptr.

解决方案:检查复制槽配置或设置备用/辅助复制槽。

level: WARNING

GS_113120188

错误码: WAL generated with full_page_writes=off was replayed since last restartpoint.

解决方案:备份已损坏,不应使用。在master上启用full_page_writes并运行CHECKPOINT。

level: ERROR

GS_113120190

错误码: the standby was promoted during online backup.

errhint:正在执行的备份已损坏,不应使用。请尝试使用另一个在线备份。

level: ERROR

GS_113120191

错误码: WAL generated with full_page_writes=off was replayed during online backup.

解决方案:备份已损坏,不应使用。在master上启用full_page_writes并运行CHECKPOINT。

level: ERROR

GS_113120192

错误码: pg_stop_backup still waiting for all required WAL segments to be archived (%d seconds elapsed).

解决方案:检查你的archive_command是否正确执行。

level: WARNING

GS_113140042

错误码: recovery is in progress.

解决方案:xlog函数、WAL控制函数在恢复期间不能执行,恢复控制函数只能在恢复期间执行,在恢复期间不能创建新的WAL条目、不能执行Roach备份。

level: ERROR

GS_113140188

错误码: a backup is already in progress.

解决方案:请确认没有正在进行的备份。

level: ERROR

GS_113150041

错误码:WAL level not sufficient for making an online roach backup.

解决方案:wal_level必须设置为archive。

level: ERROR

GS_113200318

错误码: WAL level not sufficient for creating a restore point.

解决方案:wal_level必须在服务器启动时设置为archive或hot_standby。

level: ERROR

GS_113200827

错误码: backup_label contains data inconsistent with control file.

errhint:备份已损坏,您可以使用另一个备份进行恢复。

level: FATAL

GS_113200862

错误码: WAL ends before end of online backup.

解决方案:在进行在线备份时生成的所有WAL必须在恢复时可用。

level: FATAL

GS_113201237

错误码: database files are incompatible with server.

解决方案:字节顺序可能不匹配,需要进行gs_initdb。

level: FATAL

GS_113201249

错误码: database files are incompatible with server.

解决方案:数据库集群初始化时没有使用hadove_INT64_TIMETAMP,但是服务器是使用hadove_INT64_TIMETAMP编译的。请重新编译或进行gs_initdb。

level: FATAL

GS_113201258

错误码: database system was interrupted while in recovery at %s.

解决方案:某些数据已损坏,您可以使用上次的备份进行恢复。

level: LOG

GS_113201259

错误码: database system was interrupted while in recovery at log time %s.

解决方案:如果这种情况发生多次,则某些数据可能已损坏,您可能需要选择较早的备份来恢复目标。

level: LOG

GS_113201322

错误码: hot standby is not possible because %s = %d is a lower setting than on the master server (its value was %d).

解决方案:您可能需要增加%s的值。

level: ERROR

GS_113201323

错误码: WAL was generated with wal_level=minimal.

解决方案:如果您临时设置wal_level=minimal而不进行新的基本备份,则会发生这种情况。

level: WARNING

GS_113201324

错误码: hot standby is not possible because wal_level was not set to \hot_standby\ or higher on the master server.

解决方案:在master上将wal_level设置为hot_standby。

level: ERROR