Chapter 51. Archive Modules

Chapter 51. Archive Modules
Prev	Up	Part V. Server Programming	Home	Next

Table of Contents

51.2.1. Startup Callback
51.2.2. Check Callback
51.2.3. Archive Callback
51.2.4. Shutdown Callback

+ PostgreSQL provides infrastructure to create custom modules for continuous + archiving (see Section 26.3). While archiving via + a shell command (i.e., archive_command) is much + simpler, a custom archive module will often be considerably more robust and + performant. +

+ When a custom archive_library is configured, PostgreSQL + will submit completed WAL files to the module, and the server will avoid + recycling or removing these WAL files until the module indicates that the files + were successfully archived. It is ultimately up to the module to decide what + to do with each WAL file, but many recommendations are listed at + Section 26.3.1. +

+ Archiving modules must at least consist of an initialization function (see + Section 51.1) and the required callbacks (see + Section 51.2). However, archive modules are + also permitted to do much more (e.g., declare GUCs and register background + workers). +

+ The contrib/basic_archive module contains a working + example, which demonstrates some useful techniques. +

Prev	Up	Next
Chapter 50. Replication Progress Tracking	Home	51.1. Initialization Functions