Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

checkpoint(7) [centos man page]

CHECKPOINT(7)						  PostgreSQL 9.2.7 Documentation					     CHECKPOINT(7)

NAME
CHECKPOINT - force a transaction log checkpoint SYNOPSIS
CHECKPOINT DESCRIPTION
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 Section 29.4, "WAL Configuration", in the documentation for more details about what happens during a checkpoint. The CHECKPOINT command forces an immediate checkpoint when the command is issued, without waiting for a regular checkpoint scheduled by the system (controlled by the settings in Section 18.5.2, "Checkpoints", in the documentation). CHECKPOINT is not intended for use during normal operation. If executed during recovery, the CHECKPOINT command will force a restartpoint (see Section 29.4, "WAL Configuration", in the documentation) rather than writing a new checkpoint. Only superusers can call CHECKPOINT. COMPATIBILITY
The CHECKPOINT command is a PostgreSQL language extension. PostgreSQL 9.2.7 2014-02-17 CHECKPOINT(7)

Check Out this Related Man Page

OPAL-CHECKPOINT(1)						       1.4.5							OPAL-CHECKPOINT(1)

NAME
opal-checkpoint - Checkpoint a running sequential process using the Open PAL Checkpoint/Restart Service (CRS). Note: This should only be used by the user if the application being checkpointed is an OPAL-only application. If it is an Open RTE or Open MPI program their respective tools should be used. SYNOPSIS
opal-checkpoint [ options ] <PID> Options opal-checkpoint will attempt to notify a running process that it has been requested that the process checkpoint itself. A snapshot handle reference is presented to the user, which is used in opal_restart to restart the process. <PID> Process ID of the running target process. -h | --help Display help for this command --term After checkpointing the running process, terminate it. -v | --verbose Enable verbose output for debugging. -n | --name Request a specific name for the local snapshot reference. -w | --where Request that the local snapshot reference be placed in a specific location. -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
opal-checkpoint can be invoked multiple, non-overlapping times. This allows the user to take involuntary checkpoints of a running sequen- tial process. See opal_crs(7) for more information about the CRS framework and components. 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 the running process being checkpointed. SEE ALSO
opal-restart(1), opal_crs(7) Open MPI Feb 10, 2012 OPAL-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