database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-09-02 04:21:28 +03:00
Code Activity

Pre-beta2 mechanical code beautification.

Browse Source 
Run pgindent and pgperltidy.  It seems we're still some ways
away from all committers doing this automatically.  Now that
we have a buildfarm animal that will whine about poorly-indented
code, we'll try to keep the tree more tidy.

Discussion: https://postgr.es/m/3156045.1687208823@sss.pgh.pa.us
This commit is contained in:
Tom Lane
2023-06-20 09:50:43 -04:00
parent 877bf52cff
commit b334612b8a
11 changed files with 39 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/storage/file/fd.c
View File

@@ -415,7 +415,7 @@ pg_fsync(int fd)
int
pg_fsync_no_writethrough(int fd)
{
int rc;
int rc;
if (!enableFsync)
return 0;
@@ -456,7 +456,7 @@ pg_fsync_writethrough(int fd)
int
pg_fdatasync(int fd)
{
int rc;
int rc;
if (!enableFsync)
return 0;
@@ -500,6 +500,7 @@ pg_flush_data(int fd, off_t offset, off_t nbytes)
return;
retry:
/*
* sync_file_range(SYNC_FILE_RANGE_WRITE), currently linux specific,
* tells the OS that writeback for the specified blocks should be

6
src/backend/storage/ipc/standby.c
View File

@@ -1197,9 +1197,9 @@ standby_redo(XLogReaderState *record)
/*
* The startup process currently has no convenient way to schedule
* stats to be reported. XLOG_RUNNING_XACTS records issued at a
* regular cadence, making this a convenient location to report
* stats. While these records aren't generated with wal_level=minimal,
* stats also cannot be accessed during WAL replay.
* regular cadence, making this a convenient location to report stats.
* While these records aren't generated with wal_level=minimal, stats
* also cannot be accessed during WAL replay.
*/
pgstat_report_stat(true);
}

8
src/backend/storage/smgr/md.c
View File

@@ -564,10 +564,10 @@ mdzeroextend(SMgrRelation reln, ForkNumber forknum,
Assert(segstartblock + numblocks <= RELSEG_SIZE);
/*
* If available and useful, use posix_fallocate() (via FileFallocate())
* to extend the relation. That's often more efficient than using
* write(), as it commonly won't cause the kernel to allocate page
* cache space for the extended pages.
* If available and useful, use posix_fallocate() (via
* FileFallocate()) to extend the relation. That's often more
* efficient than using write(), as it commonly won't cause the kernel
* to allocate page cache space for the extended pages.
*
* However, we don't use FileFallocate() for small extensions, as it
* defeats delayed allocation on some filesystems. Not clear where