Hi all, we are reviewing our current backup process based on the low level pg_start_backup and pg_stop_backup using the exclusive approach. During a discussion with one of my coworkers he claimed that after pg_start_backup executed, no writes into "the file system" happen anymore. The only exception he makes is writes to the WAL. >From what I understand from reading the docs and multiple other sources, I have a different opinion: The only thing pg_start_backup changes regarding writes in the data directory of Postgres is that a checkpoint is done as part of starting the backup, even if no checkpoint would be needed currently otherwise. After that is done, from my understanding, Postgres is free to write any file in the directory at any given time again however it sees fit. That's why inconsistent files are mentioned at many places: > We do not need a perfectly consistent file system backup as the > starting point.[...] https://www.postgresql.org/docs/current/continuous-archiving.html > Don’t forget that database activity, including checkpointing, > continues normally in backup mode! https://www.cybertec-postgresql.com/en/exclusive-backup-deprecated-what-now/# > Base backup does NOT prevent writes to the data directory. [...] > The key point is that the base backup is NOT a consistent copy of > the database. https://www.2ndquadrant.com/en/blog/what-does-pg_start_backup-do/ So what's the case: Does pg_start_backup put any writing limitations for Postgres in place or not? If so, I assume those would be removed by pg_stop_backup. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: Thorsten.Schoening@xxxxxxxxxx AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
