Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

checkpoint(7) [redhat man page]

CHECKPOINT(7)							   SQL Commands 						     CHECKPOINT(7)

NAME
CHECKPOINT - force a transaction log checkpoint SYNOPSIS
CHECKPOINT DESCRIPTION
Write-Ahead Logging (WAL) puts a checkpoint in the transaction log every so often. (To adjust the automatic checkpoint interval, see the run-time configuration options CHECKPOINT_SEGMENTS and CHECKPOINT_TIMEOUT.) The CHECKPOINT command forces an immediate checkpoint when the command is issued, without waiting for a scheduled checkpoint. A checkpoint is a point in the transaction log sequence at which all data files have been updated to reflect the information in the log. All data files will be flushed to disk. Refer to the PostgreSQL Administrator's Guide for more information about the WAL system. Only superusers may call CHECKPOINT. The command is not intended for use during normal operation. SEE ALSO
PostgreSQL Administrator's Guide COMPATIBILITY
The CHECKPOINT command is a PostgreSQL language extension. SQL - Language Statements 2002-11-22 CHECKPOINT(7)

Check Out this Related Man Page

OMPI-CHECKPOINT(1)						     Open MPI							OMPI-CHECKPOINT(1)

NAME
ompi-checkpoint, orte-checkpoint - Checkpoint a running parallel process using the Open MPI Checkpoint/Restart Service (CRS) NOTE: ompi-checkpoint, and orte-checkpoint are all exact synonyms for each other. Using any of the names will result in exactly identical behavior. SYNOPSIS
ompi-checkpoint [ options ] <PID_OF_MPIRUN> Options orte-checkpoint will attempt to notify a running parallel job (identified by mpirun) that it has been requested that the job checkpoint itself. A global snapshot handle reference is presented to the user, which is used in ompi_restart to restart the job. <PID_OF_MPIRUN> Process ID of the mpirun process. -h | --help Display help for this command -w | --nowait Do not wait for the application to finish checkpointing before returning. -s | --status Display status messages regarding the progression of the checkpoint request. --term After checkpointing the running job, terminate it. -v | --verbose Enable verbose output for debugging. -gmca | --gmca <key> <value> Pass global MCA parameters that are applicable to all contexts. <key> is the parameter name; <value> is the parameter value. -mca | --mca <key> <value> Send arguments to various MCA modules. DESCRIPTION
orte-checkpoint can be invoked multiple, non-overlapping times. It is convenient to note that the user does not need to spectify the checkpointer to be used here, as that is determined completely by each of the running process in the job being checkpointed. SEE ALSO
orte-ps(1), orte-clean(1), ompi-restart(1), opal-checkpoint(1), opal-restart(1), opal_crs(7) 1.4.5 Feb 10, 2012 OMPI-CHECKPOINT(1)
Man Page

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

process checkpointing

how process checkpointing is carried out ? Actually i want detail steps to carry out process checkpointing with discription of each and every file included in it like the core dump file,what is ELF header etc. (5 Replies)
Discussion started by: pratibha
5 Replies

2. UNIX for Dummies Questions & Answers

Restore Socket after checkpoint

Hello, i have done the checkpoint of an application client server in C with BLCR (Berkeley Lab checkpoint restart), after a failure, i'd like to restart server (server.blcr) and client (client.blcr) but i should recreate sockets betwen new client and new server, have you an idea please ? ... (0 Replies)
Discussion started by: chercheur857
0 Replies