|
32 | 32 | * Thus, the maximum size of a single file is RELSEG_SIZE * BLCKSZ; |
33 | 33 | * relations bigger than that are divided into multiple files. |
34 | 34 | * |
35 | | - * CAUTION: RELSEG_SIZE * BLCKSZ must be less than your OS' limit on file size. |
36 | | - * This is typically 2Gb or 4Gb in a 32-bit operating system. By default, |
37 | | - * we make the limitone billion bytes to avoid any possible integer-overflow |
| 35 | + * CAUTION: RELSEG_SIZE * BLCKSZ must be less than your OS' limit on file |
| 36 | + *size.This is typically 2Gb or 4Gb in a 32-bit operating system. By |
| 37 | + *default,we make the limit1Gb to avoid any possible integer-overflow |
38 | 38 | * problems within the OS. A limit smaller than necessary only means we |
39 | | - * divide a large relation into more chunks than necessary, so it seems best |
40 | | - * to err in the direction of a small limit. |
| 39 | + * divide a large relation into more chunks than necessary, so it seems |
| 40 | + * best to err in the direction of a small limit. (Besides, a power-of-2 |
| 41 | + * value saves a few cycles in md.c.) |
41 | 42 | * |
42 | 43 | * CAUTION: you had best do an initdb if you change either BLCKSZ or |
43 | 44 | * RELSEG_SIZE. |
44 | 45 | */ |
45 | | -#defineRELSEG_SIZE(1000000000 / BLCKSZ) |
| 46 | +#defineRELSEG_SIZE(0x40000000 / BLCKSZ) |
46 | 47 |
|
47 | 48 | /* |
48 | 49 | * The following is set using configure. |
|