xlog
GS_113040326
errmsg:syntax error in history file: %s.
errhint: Expected a numeric timeline ID.
level:FATAL
GS_113040327
errmsg:invalid data in history file: %s.
errhint: Timeline IDs must be in increasing sequence.
level:FATAL
GS_113040328
errmsg:invalid data in history file %s.
errhint: Timeline IDs must be less than child timeline's ID.
level:FATAL
GS_113040337
errmsg:recovery command file %s specified neither primary_conninfo nor restore_command.
errhint: The database server will regularly poll the pg_xlog subdirectory to check for files placed there.
level:WARNING
GS_113120083
errmsg:could not reset replication slot at the end of recovery.
errhint: Delete replication slot or increase max_replication_slots.
level:WARNING
GS_113120111
errmsg:Could not locate required checkpoint record.
errhint: If you are not restoring from a backup, try removing the file "%s/backup_label".
level:FATAL
GS_113120112
errmsg:could not find redo location referenced by checkpoint record.
errhint: If you are not restoring from a backup, try removing the file "%s/backup_label".
level:FATAL
GS_113120168
errmsg:invalid replication slot recptr.
errhint: Check slot configuration or setup standby/secondary.
level:WARNING
GS_113120188
errmsg:WAL generated with full_page_writes=off was replayed since last restartpoint.
errhint: This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master.
level:ERROR
GS_113120190
errmsg:the standby was promoted during online backup.
errhint: This means that the backup being taken is corrupt and should not be used. Try taking another online backup.
level:ERROR
GS_113120191
errmsg:WAL generated with full_page_writes=off was replayed during online backup.
errhint: This means that the backup being taken on the standby is corrupt and should not be used. Enable full_page_writes and run CHECKPOINT on the master.
level:ERROR
GS_113120192
errmsg:pg_stop_backup still waiting for all required WAL segments to be archived (%d seconds elapsed).
errhint: Check that your archive_command is executing properly. pg_stop_backup can be canceled safely.
level:WARNING
GS_113140042
errmsg:recovery is in progress.
errhint: This xlog function cannot be executed during recovery.WAL control functions cannot be executed during recovery.Recovery control functions can only be executed during recovery.Cannot make new WAL entries during recovery.Roach backup cannot be executed during recovery.
level:ERROR
GS_113140188
errmsg:a backup is already in progress.
errhint: If you're sure there is no backup in progress.
level:ERROR
GS_113150041
errmsg:WAL level not sufficient for making an online roach backup.
errhint: wal_level must be set to archive.
level:ERROR
GS_113200318
errmsg:WAL level not sufficient for creating a restore point.
errhint: wal_level must be set to \archive\ or \hot_standby\ at server start.
level:ERROR
GS_113200827
errmsg:backup_label contains data inconsistent with control file.
errhint: This means that the backup is corrupted and you will have to use another backup for recovery.
level:FATAL
GS_113200862
errmsg:WAL ends before end of online backup.
errhint: All WAL generated while online backup was taken must be available at recovery.
level:FATAL
GS_113201237
errmsg:database files are incompatible with server.
errhint: This could be a problem of mismatched byte ordering. It looks like you need to gs_initdb.
level:FATAL
GS_113201249
errmsg:database files are incompatible with server.
errdetail: The database cluster was initialized without HAVE_INT64_TIMESTAMP but the server was compiled with HAVE_INT64_TIMESTAMP.
errhint: It looks like you need to recompile or gs_initdb.
level:FATAL
GS_113201258
errmsg:database system was interrupted while in recovery at %s.
errhint: This probably means that some data is corrupted and you will have to use the last backup for recovery.
level:LOG
GS_113201259
errmsg:database system was interrupted while in recovery at log time %s.
errhint: If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
level:LOG
GS_113201322
errmsg:hot standby is not possible because %s = %d is a lower setting than on the master server (its value was %d).
errhint: You might need to increase the value of %s.
level:ERROR
GS_113201323
errmsg:WAL was generated with wal_level=minimal.
errhint: This happens if you temporarily set wal_level=minimal without taking a new base backup.
level:WARNING
GS_113201324
errmsg:hot standby is not possible because wal_level was not set to \hot_standby\ or higher on the master server.
errhint: Either set wal_level to \hot_standby\ on the master.
level:ERROR
GS_113201383
errmsg:recovery is in progress.
errhint: WAL control functions cannot be executed during recovery.
level:ERROR
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot