diff options
author | Marc G. Fournier <scrappy@hub.org> | 1998-01-13 04:05:12 +0000 |
---|---|---|
committer | Marc G. Fournier <scrappy@hub.org> | 1998-01-13 04:05:12 +0000 |
commit | 374bb5d2610d0f520abbc602bbf1d6b9c533f335 (patch) | |
tree | 1d0fbc84ce15ea7d9d077ecad5cf96a0ec8a69c5 /src/backend/access/gist/gistget.c | |
parent | f0445dcbc417f03b79f4502570732924b39e5cc5 (diff) | |
download | postgresql-374bb5d2610d0f520abbc602bbf1d6b9c533f335.tar.gz postgresql-374bb5d2610d0f520abbc602bbf1d6b9c533f335.zip |
Some *very* major changes by darrenk@insightdist.com (Darren King)
==========================================
What follows is a set of diffs that cleans up the usage of BLCKSZ.
As a side effect, the person compiling the code can change the
value of BLCKSZ _at_their_own_risk_. By that, I mean that I've
tried it here at 4096 and 16384 with no ill-effects. A value
of 4096 _shouldn't_ affect much as far as the kernel/file system
goes, but making it bigger than 8192 can have severe consequences
if you don't know what you're doing. 16394 worked for me, _BUT_
when I went to 32768 and did an initdb, the SCSI driver broke and
the partition that I was running under went to hell in a hand
basket. Had to reboot and do a good bit of fsck'ing to fix things up.
The patch can be safely applied though. Just leave BLCKSZ = 8192
and everything is as before. It basically only cleans up all of the
references to BLCKSZ in the code.
If this patch is applied, a comment in the config.h file though above
the BLCKSZ define with warning about monkeying around with it would
be a good idea.
Darren darrenk@insightdist.com
(Also cleans up some of the #includes in files referencing BLCKSZ.)
==========================================
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions