From dd7ea37c435e10f9c5aa3fb257a05c08814a4ad2 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Mon, 4 Mar 2024 14:37:13 -0500 Subject: [PATCH] Fix pgindent damage. Apparently, I neglected to pgindent the prior commit. Per buildfarm. --- src/backend/backup/basebackup_incremental.c | 4 +-- src/backend/postmaster/walsummarizer.c | 34 ++++++++++----------- 2 files changed, 19 insertions(+), 19 deletions(-) diff --git a/src/backend/backup/basebackup_incremental.c b/src/backend/backup/basebackup_incremental.c index a8f2e72e7b1..ebc41f28be5 100644 --- a/src/backend/backup/basebackup_incremental.c +++ b/src/backend/backup/basebackup_incremental.c @@ -778,8 +778,8 @@ GetFileBackupMethod(IncrementalBackupInfo *ib, const char *path, } /* - * Look up the special block reference table entry for the database as - * a whole. + * Look up the special block reference table entry for the database as a + * whole. */ rlocator.spcOid = spcoid; rlocator.dbOid = dboid; diff --git a/src/backend/postmaster/walsummarizer.c b/src/backend/postmaster/walsummarizer.c index 5a8006ea4c7..8bf8a03471a 100644 --- a/src/backend/postmaster/walsummarizer.c +++ b/src/backend/postmaster/walsummarizer.c @@ -1089,25 +1089,25 @@ SummarizeDbaseRecord(XLogReaderState *xlogreader, BlockRefTable *brtab) uint8 info = XLogRecGetInfo(xlogreader) & ~XLR_INFO_MASK; /* - * We use relfilenode zero for a given database OID and tablespace OID - * to indicate that all relations with that pair of IDs have been - * recreated if they exist at all. Effectively, we're setting a limit - * block of 0 for all such relfilenodes. + * We use relfilenode zero for a given database OID and tablespace OID to + * indicate that all relations with that pair of IDs have been recreated + * if they exist at all. Effectively, we're setting a limit block of 0 for + * all such relfilenodes. * * Technically, this special handling is only needed in the case of - * XLOG_DBASE_CREATE_FILE_COPY, because that can create a whole bunch - * of relation files in a directory without logging anything - * specific to each one. If we didn't mark the whole DB OID/TS OID - * combination in some way, then a tablespace that was dropped after - * the reference backup and recreated using the FILE_COPY method prior - * to the incremental backup would look just like one that was never - * touched at all, which would be catastrophic. + * XLOG_DBASE_CREATE_FILE_COPY, because that can create a whole bunch of + * relation files in a directory without logging anything specific to each + * one. If we didn't mark the whole DB OID/TS OID combination in some way, + * then a tablespace that was dropped after the reference backup and + * recreated using the FILE_COPY method prior to the incremental backup + * would look just like one that was never touched at all, which would be + * catastrophic. * - * But it seems best to adopt this treatment for all records that drop - * or create a DB OID/TS OID combination. That's similar to how we - * treat the limit block for individual relations, and it's an extra - * layer of safety here. We can never lose data by marking more stuff - * as needing to be backed up in full. + * But it seems best to adopt this treatment for all records that drop or + * create a DB OID/TS OID combination. That's similar to how we treat the + * limit block for individual relations, and it's an extra layer of safety + * here. We can never lose data by marking more stuff as needing to be + * backed up in full. */ if (info == XLOG_DBASE_CREATE_FILE_COPY) { @@ -1136,7 +1136,7 @@ SummarizeDbaseRecord(XLogReaderState *xlogreader, BlockRefTable *brtab) { xl_dbase_drop_rec *xlrec; RelFileLocator rlocator; - int i; + int i; xlrec = (xl_dbase_drop_rec *) XLogRecGetData(xlogreader); rlocator.dbOid = xlrec->db_id;