mirror of
https://github.com/postgres/postgres.git
synced 2026-03-02 05:13:42 -05:00
2b67dc5387
ALLOC_BIGCHUNK_LIMIT are always allocated as separate malloc() blocks, and are free()d immediately upon pfree(). Also, if such a chunk is enlarged with repalloc(), translate the operation into a realloc() so as to minimize memory usage. Of course, these large chunks still get freed automatically if the alloc set is reset. I have set ALLOC_BIGCHUNK_LIMIT at 64K for now, but perhaps another size would be better? |
||
|---|---|---|
| .. | ||
| backend | ||
| bin | ||
| corba | ||
| data | ||
| include | ||
| interfaces | ||
| lextest | ||
| makefiles | ||
| pl | ||
| template | ||
| test | ||
| tools | ||
| tutorial | ||
| utils | ||
| win32 | ||
| config.guess | ||
| config.sub | ||
| configure | ||
| configure.in | ||
| DEVELOPERS | ||
| GNUmakefile.in | ||
| install-sh | ||
| Makefile | ||
| Makefile.global.in | ||
| Makefile.shlib | ||
| win32.mak | ||