the only problem is because if we need to tune Postermaster to use
large buffer while system havn't so many SYSV shared memory, in many
systemes, we need to recompile OS kernel, this is a small problem to install
PGSQL to product environment.
Of course, if you haven't got mmap(), a recompile
On Mon, 26 Feb 2001, Bruce Momjian wrote:
the only problem is because if we need to tune Postermaster to use
large buffer while system havn't so many SYSV shared memory, in many
systemes, we need to recompile OS kernel, this is a small problem to install
PGSQL to product environment.
the only problem is because if we need to tune Postermaster to use
large buffer while system havn't so many SYSV shared memory, in many
systemes, we need to recompile OS kernel, this is a small problem to install
PGSQL to product environment.
What? You don't automatically recompile
Okay ... same applies to MMAP() though, I had to disappoint ... there are
kernel limits that, at least under FreeBSD, do require a kernel
recompile in order to exceed ... alot of them have been moved (maybe all
now) to sysctl settable values ... but, again, under some of the
commercial OSs,
On Mon, 26 Feb 2001, Bruce Momjian wrote:
Okay ... same applies to MMAP() though, I had to disappoint ... there are
kernel limits that, at least under FreeBSD, do require a kernel
recompile in order to exceed ... alot of them have been moved (maybe all
now) to sysctl settable values ...
But the mmap() limits are much larger than the SysV limits, aren't they,
to the point where you would never have to fiddle with the mmap() limits
to get 100mb of buffers, right?
Not necessarily ... it depends on the admin of the server ... then again,
I don't consider it a hassle to add
Bruce Momjian [EMAIL PROTECTED] writes:
I know it is easy for you, but the number of reports and problems we
hear about shows it is an issue for some.
We hear some reports, but not a lot. We have no idea whatever what
problems might ensue if we used mmap instead. I'm dubious that SysV
shmem
