mirror of
https://git.postgresql.org/git/postgresql.git
synced 2026-02-14 10:27:04 +08:00
8d140c5822
* sync_method is renamed to wal_sync_method. * sync_method_options[] is renamed to wal_sync_method_options[]. * assign_xlog_sync_method() is renamed to assign_wal_sync_method(). * The names of the available synchronization methods are now prefixed with "WAL_SYNC_METHOD_" and have been moved into a WalSyncMethod enum. * PLATFORM_DEFAULT_SYNC_METHOD is renamed to PLATFORM_DEFAULT_WAL_SYNC_METHOD, and DEFAULT_SYNC_METHOD is renamed to DEFAULT_WAL_SYNC_METHOD. These more descriptive names help distinguish the code for wal_sync_method from the code for DataDirSyncMethod (e.g., the recovery_init_sync_method configuration parameter and the --sync-method option provided by several frontend utilities). This change also prevents name collisions between the aforementioned sets of code. Since this only improves the naming of internal identifiers, there should be no behavior change. Author: Maxim Orlov Discussion: https://postgr.es/m/CACG%3DezbL1gwE7_K7sr9uqaCGkWhmvRTcTEnm3%2BX1xsRNwbXULQ%40mail.gmail.com
23 lines
1.0 KiB
C
23 lines
1.0 KiB
C
/* src/include/port/linux.h */
|
|
|
|
/*
|
|
* As of July 2007, all known versions of the Linux kernel will sometimes
|
|
* return EIDRM for a shmctl() operation when EINVAL is correct (it happens
|
|
* when the low-order 15 bits of the supplied shm ID match the slot number
|
|
* assigned to a newer shmem segment). We deal with this by assuming that
|
|
* EIDRM means EINVAL in PGSharedMemoryIsInUse(). This is reasonably safe
|
|
* since in fact Linux has no excuse for ever returning EIDRM; it doesn't
|
|
* track removed segments in a way that would allow distinguishing them from
|
|
* private ones. But someday that code might get upgraded, and we'd have
|
|
* to have a kernel version test here.
|
|
*/
|
|
#define HAVE_LINUX_EIDRM_BUG
|
|
|
|
/*
|
|
* Set the default wal_sync_method to fdatasync. With recent Linux versions,
|
|
* xlogdefs.h's normal rules will prefer open_datasync, which (a) doesn't
|
|
* perform better and (b) causes outright failures on ext4 data=journal
|
|
* filesystems, because those don't support O_DIRECT.
|
|
*/
|
|
#define PLATFORM_DEFAULT_WAL_SYNC_METHOD WAL_SYNC_METHOD_FDATASYNC
|