Thread: installation options
First, I am installing postgres 7.02 on i686, 2CPU, 512mb, mandrake linux 7.1. I have set the max backends switch to 256 during the compile (--with-maxbackends=256) along with the rest of the chosen parameters but I am a little puzzled about the buffer size and number. I have read the number of buffers can be set by the -B switch at startup. Is this necessary, since I changed the max backends to 256? I guess then buffers should be 512, but was the default number of buffers changed when I set the max backends to 256? Also what is the best way to calculate the block size needed? Steve Ackerman Web Developer GoShip.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
It seems no one is monitoring the novice list... I sent the message yesterday and I am still stumped... I would assume setting the --maxbackends to 256 also changes the default buffers from 64 to 512, right? If not is this only done with the -B switch? Thank you, Steve > > First, I am installing postgres 7.02 on i686, 2CPU, 512mb, mandrake linux > 7.1. > > I have set the max backends switch to 256 during the compile > (--with-maxbackends=256) along with the rest of the chosen > parameters but I > am a little puzzled about the buffer size and number. I have read > the number > of buffers can be set by the -B switch at startup. Is this > necessary, since > I changed the max backends to 256? I guess then buffers should be 512, but > was the default number of buffers changed when I set the max backends to > 256? > > Also what is the best way to calculate the block size needed? > > Steve Ackerman > Web Developer > GoShip.com > > __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com
Hello all. I'm having some trouble with ODBC under 2000. I cannot install the PostODBC driver. It'll get ready to bring up the installation program(after going to 100% starting the install wizard) and freezes. It does not recover(even after an hour's time while I was cooking diner). So, I am left without ODBC access. This is a problem... :) I've looked on the www.openlinksw.com site, but I am not clear what to download. I downloaded their multi-tier for the appropriate client system, but the installation program mentioned nothing of postgres; the webpage clearly does. I'd appreciate some help getting this going. Thanks, Jacob Joseph PS, If there's a different method of linking to MS Access, I'm open to all suggestions.
"Steve Ackerman" <sacker3254@yahoo.com> writes:
> setting the --maxbackends to 256 also changes the default buffers from 64 to
> 512, right? If not is this only done with the -B switch?
AFAIR, -N (--maxbackends) *only* sets the max # of backends. You should
also specify an appropriate number of shared buffers (-B). The
postmaster enforces a minimum -B setting of twice -N, but that's
probably on the low side --- if you're thinking -N of 100 or so,
I'd suggest -B of 500 to 1000, maybe more.
Feel free to experiment and report back on what seems to work well
for your application mix...
regards, tom lane
I'm not sure you've got the right driver. Try this one: ftp://ftp.postgresql.org/pub/odbc/latest/postdrv.exe Poul L. Christiansen Jacob Joseph wrote: > > Hello all. I'm having some trouble with ODBC under 2000. I cannot install > the PostODBC driver. It'll get ready to bring up the installation > program(after going to 100% starting the install wizard) and freezes. It > does not recover(even after an hour's time while I was cooking diner). So, > I am left without ODBC access. This is a problem... :) > > I've looked on the www.openlinksw.com site, but I am not clear what to > download. I downloaded their multi-tier for the appropriate client system, > but the installation program mentioned nothing of postgres; the webpage > clearly does. > > I'd appreciate some help getting this going. > > Thanks, > Jacob Joseph > > PS, If there's a different method of linking to MS Access, I'm open to all > suggestions.