flattener( new MyFlattener()) // Default: DefaultFlattener cleanStrategy( new FileLastModifiedCleanStrategy( MAX_TIME)) // Default: NeverCleanStrategy() backupStrategy( new NeverBackupStrategy()) // Default: FileSizeBackupStrategy(1024 * 1024) fileNameGenerator( new DateFileNameGenerator()) // Default: ChangelessFileNameGenerator('log') Builder( '') // Specify the directory path of log file(s) Printer androidPrinter = new AndroidPrinter( true) // Printer that print the log using Printer consolePrinter = new ConsolePrinter() // Printer that print the log to console using System.out Printer filePrinter = new FilePrinter // Printer that print(save) the log to file addInterceptor( new MyInterceptor()) // Add other log interceptor addInterceptor( new BlacklistTagsFilterInterceptor( // Add blacklist tags filter 'blacklist1', 'blacklist2', 'blacklist3'))

class, // Add formatter for specific class of object new An圜lassObjectFormatter()) // Use Object.toString() by default borderFormatter( new MyBoardFormatter()) // Default: DefaultBorderFormatter stackTraceFormatter( new MyStackTraceFormatter()) // Default: DefaultStackTraceFormatter threadFormatter( new MyThreadFormatter()) // Default: DefaultThreadFormatter throwableFormatter( new MyThrowableFormatter()) // Default: DefaultThrowableFormatter xmlFormatter( new MyXmlFormatter()) // Default: DefaultXmlFormatter jsonFormatter( new MyJsonFormatter()) // Default: DefaultJsonFormatter enableBorder() // Enable border, disabled by default enableStackTrace( 2) // Enable stack trace info with depth 2, disabled by default enableThreadInfo() // Enable thread info, disabled by default tag( 'MY_TAG') // Specify TAG, default: 'X-LOG' ALL // Specify log level, logs below this level won't be printed, default: LogLevel.ALL However, the number returned there is actually the 'time since the last replayed transaction from the master' - so if the master hasn't had a transaction in awhile that 'time' might make it seem like the slave is falling behind (when it reality, it is caught up, but there have been no transactions on the master.LogConfiguration config = new LogConfiguration. Pg_last_xact_replay_timestamp())) AS time_lag On the slave you can get an idea of the time delay using the query: SELECT extract(epoch from (now(). Of course, if the slave is replaying slowly it might never catch up - but you can measure if it is 'catching up' or 'falling behind' (sort of) using the query below: Technically it's 'possible' for a slave to catch up with the master if the log files that the slave needs are still available on the master. You could locate the current WAL file name in use using: select pg_xlogfile_name(pg_current_xlog_insert_location()) The part before the '/' is multiplied by 'ff000000' and added to the second part: If you take the output of: SELECT pg_current_xlog_location() you'll get something like: 70/A9002358

The log unit are in bytes (though they are relative - so they aren't useful for measuring anything other than 'offsets', and there sometimes can be 'jumps' where there's a lot of skipped bytes), with the value being computed as:

Xlog signoressa