Determine max_connections first, then see how large shared_buffers can

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 87299583a5004df4b563226349c906f2184dd1b0
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2003-10-13T21:06:44Z
Releases: 7.4.1
Determine max_connections first, then see how large shared_buffers can
be made, to avoid corner cases where max_connections ends up unreasonably
small because shared_buffers is hogging too much shmem space.  Per pghackers
discussion about a week ago.  Also, fix the copy-newlines problem in a
more robust way, by using COPY FROM filename instead of COPY FROM STDIN;
per a suggestion from Peter.

Files

PathChange+/−
src/bin/initdb/initdb.sh modified +15 −15