diff options
author | Tom Lane | 2008-05-02 03:41:46 +0000 |
---|---|---|
committer | Tom Lane | 2008-05-02 03:41:46 +0000 |
commit | 02ecdf64eb77f0ee0eabbfb5bdbcdf1e3820b3cc (patch) | |
tree | 547f204571467163bc06444010ab65af37d3fdb7 | |
parent | 43ba7bfb2c9a5fe3ab37e7453a7bddfd693499ef (diff) |
Sigh ... pg_config.h.win32 needs to define BLCKSZ and RELSEG_SIZE now.
-rw-r--r-- | src/include/pg_config.h.win32 | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/src/include/pg_config.h.win32 b/src/include/pg_config.h.win32 index 1c7e3cd2d0..49892c24ec 100644 --- a/src/include/pg_config.h.win32 +++ b/src/include/pg_config.h.win32 @@ -37,6 +37,15 @@ /* The alignment requirement of a `short'. */ #define ALIGNOF_SHORT 2 +/* Size of a disk block --- this also limits the size of a tuple. You can set + it bigger if you need bigger tuples (although TOAST should reduce the need + to have large tuples, since fields can be spread across multiple tuples). + BLCKSZ must be a power of 2. The maximum possible value of BLCKSZ is + currently 2^15 (32768). This is determined by the 15-bit widths of the + lp_off and lp_len fields in ItemIdData (see include/storage/itemid.h). + Changing BLCKSZ requires an initdb. */ +#define BLCKSZ 8192 + /* Define to the default TCP port number on which the server listens and to which clients will try to connect. This can be overridden at run-time, but it's convenient if your clients have the right default compiled in. @@ -591,6 +600,19 @@ your system. */ /* #undef PTHREAD_CREATE_JOINABLE */ +/* RELSEG_SIZE is the maximum number of blocks allowed in one disk file. Thus, + the maximum size of a single file is RELSEG_SIZE * BLCKSZ; relations bigger + than that are divided into multiple files. RELSEG_SIZE * BLCKSZ must be + less than your OS' limit on file size. This is often 2 GB or 4GB in a + 32-bit operating system, unless you have large file support enabled. By + default, we make the limit 1 GB to avoid any possible integer-overflow + problems within the OS. A limit smaller than necessary only means we divide + a large relation into more chunks than necessary, so it seems best to err + in the direction of a small limit. A power-of-2 value is recommended to + save a few cycles in md.c, but is not absolutely required. Changing + RELSEG_SIZE requires an initdb. */ +#define RELSEG_SIZE 131072 + /* The size of a `size_t', as computed by sizeof. */ #define SIZEOF_SIZE_T 4 |