Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

checkpoint(7) [suse 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 in the documentation for more information about the WAL system. Only superusers can call CHECKPOINT. The command is not intended for use during normal operation. COMPATIBILITY
The CHECKPOINT command is a PostgreSQL language extension. SQL - Language Statements 2010-05-14 CHECKPOINT(7)

Check Out this Related Man Page

VIRTUOSO-T(1)															     VIRTUOSO-T(1)

NAME
virtuoso-t - OpenLink Virtuoso Opensource Server SYNOPSIS
virtuoso-t [-fcnCbDARwMKrBd] [+foreground] [+configfile arg] [+no-checkpoint] [+checkpoint-only] [+backup-dump] [+crash-dump] [+configfile arg] [+restore-crash-dump] [+wait] [+more arg] [+dumpkeys arg] [+restore-backup arg] [+backup-dirs arg] [+debug] [+pwdold arg] [+pwddba arg] [+pwddav arg] virtuoso-t [+help] DESCRIPTION
This manual page documents briefly the virtuoso-t command. This manual page was written for the Debian distribution because the original program does not have a manual page. Instead, it has docu- mentation in the 'doc' VAD package. virtuoso-t is the OpenLink Virtuoso server OPTIONS
A summary of options is included below. For a complete description, see the 'doc' VAD package. +foreground run in the foreground +configfile use alternate configuration file +no-checkpoint do not checkpoint on startup +checkpoint-only exit as soon as checkpoint on startup is complete +backup-dump dump database into the transaction log, then exit +crash-dump dump inconsistent database into the transaction log, then exit +crash-dump-data-ini specify the DB ini to use for reading the data to dump +restore-crash-dump restore from a crash-dump +wait wait for background initialization to complete +mode specify mode options for server startup (onbalr) +dumpkeys specify key id(s) to dump on crash dump (default : all) +restore-backup default backup directories +backup-dirs run in the foreground +debug Show additional debugging info +pwdold Old DBA password +pwddba New DBA password +pwddav New DAV password FILES
/etc/virtuoso/virtuoso.ini The configuration file to control the behaviour of the main instance of virtuoso-t. SEE ALSO
The programs are documented fully by the 'doc' VAD package. 17 April 2013 VIRTUOSO-T(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