diff options
| author | Robert Haas <rhaas@postgresql.org> | 2024-06-28 10:45:51 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2024-06-28 10:51:05 -0400 |
| commit | b48f275f18d7da4f4863888ad047cbd699698880 (patch) | |
| tree | 946d5071a5b09f125c0706372ff92e554bbcd801 /src | |
| parent | 716bd12d22c53d1943d41309f2dd061ec601dd5e (diff) | |
| download | postgresql-b48f275f18d7da4f4863888ad047cbd699698880.tar.gz postgresql-b48f275f18d7da4f4863888ad047cbd699698880.zip | |
pgindent, because I forgot to do that.
Commit 065583cf460f980a182498941ac52810f709a897 should have
included these changes.
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/postmaster/walsummarizer.c | 23 |
1 files changed, 11 insertions, 12 deletions
diff --git a/src/backend/postmaster/walsummarizer.c b/src/backend/postmaster/walsummarizer.c index 7f987af40d0..55dc2ea8f53 100644 --- a/src/backend/postmaster/walsummarizer.c +++ b/src/backend/postmaster/walsummarizer.c @@ -505,10 +505,10 @@ GetOldestUnsummarizedLSN(TimeLineID *tli, bool *lsn_is_exact) return InvalidXLogRecPtr; /* - * If we are not the WAL summarizer process, then we normally just want - * to read the values from shared memory. However, as an exception, if - * shared memory hasn't been initialized yet, then we need to do that so - * that we can read legal values and not remove any WAL too early. + * If we are not the WAL summarizer process, then we normally just want to + * read the values from shared memory. However, as an exception, if shared + * memory hasn't been initialized yet, then we need to do that so that we + * can read legal values and not remove any WAL too early. */ if (!am_wal_summarizer) { @@ -532,8 +532,8 @@ GetOldestUnsummarizedLSN(TimeLineID *tli, bool *lsn_is_exact) * Find the oldest timeline on which WAL still exists, and the earliest * segment for which it exists. * - * Note that we do this every time the WAL summarizer process restarts - * or recovers from an error, in case the contents of pg_wal have changed + * Note that we do this every time the WAL summarizer process restarts or + * recovers from an error, in case the contents of pg_wal have changed * under us e.g. if some files were removed, either manually - which * shouldn't really happen, but might - or by postgres itself, if * summarize_wal was turned off and then back on again. @@ -582,16 +582,15 @@ GetOldestUnsummarizedLSN(TimeLineID *tli, bool *lsn_is_exact) errmsg_internal("no WAL found on timeline %u", latest_tli)); /* - * If we're the WAL summarizer, we always want to store the values we - * just computed into shared memory, because those are the values we're - * going to use to drive our operation, and so they are the authoritative + * If we're the WAL summarizer, we always want to store the values we just + * computed into shared memory, because those are the values we're going + * to use to drive our operation, and so they are the authoritative * values. Otherwise, we only store values into shared memory if shared * memory is uninitialized. Our values are not canonical in such a case, - * but it's better to have something than nothing, to guide WAL - * retention. + * but it's better to have something than nothing, to guide WAL retention. */ LWLockAcquire(WALSummarizerLock, LW_EXCLUSIVE); - if (am_wal_summarizer|| !WalSummarizerCtl->initialized) + if (am_wal_summarizer || !WalSummarizerCtl->initialized) { WalSummarizerCtl->initialized = true; WalSummarizerCtl->summarized_lsn = unsummarized_lsn; |