mirror of https://github.com/postgres/postgres
parts. Standardize spelling of comments in pg_config.h.WIN32_DEV
Peter Eisentraut
23 years ago
parent
d7c333eb9a
commit
cb1d036acb
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,212 @@ |
||||
/*------------------------------------------------------------------------
|
||||
* PostgreSQL manual configuration settings |
||||
* |
||||
* This file contains various configuration symbols and limits. In |
||||
* all cases, changing them is only useful in very rare situations or |
||||
* for developers. If you edit any of these, be sure to do a *full* |
||||
* rebuild (and an initdb if noted). |
||||
* |
||||
* $Id: pg_config_manual.h,v 1.1 2003/04/06 22:45:23 petere Exp $ |
||||
*------------------------------------------------------------------------ |
||||
*/ |
||||
|
||||
/*
|
||||
* 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 |
||||
|
||||
/*
|
||||
* 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. (Besides, a power-of-2 value |
||||
* saves a few cycles in md.c.) |
||||
* |
||||
* Changing RELSEG_SIZE requires an initdb. |
||||
*/ |
||||
#define RELSEG_SIZE (0x40000000 / BLCKSZ) |
||||
|
||||
/*
|
||||
* Maximum number of columns in an index and maximum number of |
||||
* arguments to a function. They must be the same value. |
||||
* |
||||
* The minimum value is 8 (index creation uses 8-argument functions). |
||||
* There is no specific upper limit, although large values will waste |
||||
* system-table space and processing time. |
||||
* |
||||
* Changing these requires an initdb. |
||||
*/ |
||||
#define INDEX_MAX_KEYS 32 |
||||
#define FUNC_MAX_ARGS INDEX_MAX_KEYS |
||||
|
||||
/*
|
||||
* Define this to make libpgtcl's "pg_result -assign" command process |
||||
* C-style backslash sequences in returned tuple data and convert |
||||
* PostgreSQL array values into Tcl lists. CAUTION: This conversion |
||||
* is *wrong* unless you install the routines in |
||||
* contrib/string/string_io to make the server produce C-style |
||||
* backslash sequences in the first place. |
||||
*/ |
||||
/* #define TCL_ARRAYS */ |
||||
|
||||
/*
|
||||
* User locks are handled totally on the application side as long term |
||||
* cooperative locks which extend beyond the normal transaction |
||||
* boundaries. Their purpose is to indicate to an application that |
||||
* someone is `working' on an item. Define this flag to enable user |
||||
* locks. You will need the loadable module user-locks.c to use this |
||||
* feature. |
||||
*/ |
||||
#define USER_LOCKS |
||||
|
||||
/*
|
||||
* Define this if you want psql to _always_ ask for a username and a |
||||
* password for password authentication. |
||||
*/ |
||||
/* #define PSQL_ALWAYS_GET_PASSWORDS */ |
||||
|
||||
/*
|
||||
* Define this if you want to allow the lo_import and lo_export SQL |
||||
* functions to be executed by ordinary users. By default these |
||||
* functions are only available to the Postgres superuser. CAUTION: |
||||
* These functions are SECURITY HOLES since they can read and write |
||||
* any file that the PostgreSQL server has permission to access. If |
||||
* you turn this on, don't say we didn't warn you. |
||||
*/ |
||||
/* #define ALLOW_DANGEROUS_LO_FUNCTIONS */ |
||||
|
||||
/*
|
||||
* MAXPGPATH: standard size of a pathname buffer in PostgreSQL (hence, |
||||
* maximum usable pathname length is one less). |
||||
* |
||||
* We'd use a standard system header symbol for this, if there weren't |
||||
* so many to choose from: MAXPATHLEN, MAX_PATH, PATH_MAX are all |
||||
* defined by different "standards", and often have different values |
||||
* on the same platform! So we just punt and use a reasonably |
||||
* generous setting here. |
||||
*/ |
||||
#define MAXPGPATH 1024 |
||||
|
||||
/*
|
||||
* DEFAULT_MAX_EXPR_DEPTH: default value of max_expr_depth SET variable. |
||||
*/ |
||||
#define DEFAULT_MAX_EXPR_DEPTH 10000 |
||||
|
||||
/*
|
||||
* PG_SOMAXCONN: maximum accept-queue length limit passed to |
||||
* listen(2). You'd think we should use SOMAXCONN from |
||||
* <sys/socket.h>, but on many systems that symbol is much smaller |
||||
* than the kernel's actual limit. In any case, this symbol need be |
||||
* twiddled only if you have a kernel that refuses large limit values, |
||||
* rather than silently reducing the value to what it can handle |
||||
* (which is what most if not all Unixen do). |
||||
*/ |
||||
#define PG_SOMAXCONN 10000 |
||||
|
||||
/*
|
||||
* You can try changing this if you have a machine with bytes of |
||||
* another size, but no guarantee... |
||||
*/ |
||||
#define BITS_PER_BYTE 8 |
||||
|
||||
/*
|
||||
* Define this if your operating system supports AF_UNIX family |
||||
* sockets. |
||||
*/ |
||||
#if !defined(__QNX__) && !defined(__BEOS__) |
||||
# define HAVE_UNIX_SOCKETS 1 |
||||
#endif |
||||
|
||||
/*
|
||||
* This is the default directory in which AF_UNIX socket files are |
||||
* placed. Caution: changing this risks breaking your existing client |
||||
* applications, which are likely to continue to look in the old |
||||
* directory. But if you just hate the idea of sockets in /tmp, |
||||
* here's where to twiddle it. You can also override this at runtime |
||||
* with the postmaster's -k switch. |
||||
*/ |
||||
#define DEFAULT_PGSOCKET_DIR "/tmp" |
||||
|
||||
/*
|
||||
* Defining this will make float4 and float8 operations faster by |
||||
* suppressing overflow/underflow checks. |
||||
*/ |
||||
/* #define UNSAFE_FLOATS */ |
||||
|
||||
/*
|
||||
* The random() function is expected to yield values between 0 and |
||||
* MAX_RANDOM_VALUE. Currently, all known implementations yield |
||||
* 0..2^31-1, so we just hardwire this constant. We could do a |
||||
* configure test if it proves to be necessary. CAUTION: Think not to |
||||
* replace this with RAND_MAX. RAND_MAX defines the maximum value of |
||||
* the older rand() function, which is often different from --- and |
||||
* considerably inferior to --- random(). |
||||
*/ |
||||
#define MAX_RANDOM_VALUE (0x7FFFFFFF) |
||||
|
||||
|
||||
/*
|
||||
*------------------------------------------------------------------------ |
||||
* The following symbols are for enabling debugging code, not for |
||||
* controlling user-visible features or resource limits. |
||||
*------------------------------------------------------------------------ |
||||
*/ |
||||
|
||||
/*
|
||||
* Define this to cause pfree()'d memory to be cleared immediately, to |
||||
* facilitate catching bugs that refer to already-freed values. XXX |
||||
* Right now, this gets defined automatically if --enable-cassert. In |
||||
* the long term it probably doesn't need to be on by default. |
||||
*/ |
||||
#ifdef USE_ASSERT_CHECKING |
||||
#define CLOBBER_FREED_MEMORY |
||||
#endif |
||||
|
||||
/*
|
||||
* Define this to check memory allocation errors (scribbling on more |
||||
* bytes than were allocated). Right now, this gets defined |
||||
* automatically if --enable-cassert. In the long term it probably |
||||
* doesn't need to be on by default. |
||||
*/ |
||||
#ifdef USE_ASSERT_CHECKING |
||||
#define MEMORY_CONTEXT_CHECKING |
||||
#endif |
||||
|
||||
/*
|
||||
* Define this to force all parse and plan trees to be passed through |
||||
* copyObject(), to facilitate catching errors and omissions in |
||||
* copyObject(). |
||||
*/ |
||||
/* #define COPY_PARSE_PLAN_TREES */ |
||||
|
||||
/*
|
||||
* Enable debugging print statements for lock-related operations. |
||||
*/ |
||||
/* #define LOCK_DEBUG */ |
||||
|
||||
/*
|
||||
* Other debug #defines (documentation, anyone?) |
||||
*/ |
||||
/* #define IPORTAL_DEBUG */ |
||||
/* #define HEAPDEBUGALL */ |
||||
/* #define ISTRATDEBUG */ |
||||
/* #define ACLDEBUG */ |
||||
/* #define RTDEBUG */ |
||||
/* #define GISTDEBUG */ |
||||
Loading…
Reference in new issue