Jim,
this is copied from /etc/rc...
\
if [ -f /etc/sysctl.conf ]; then
awk '{ if (!index($1, "#") && index($1, "="))
print $1 }' < /etc/sysctl.conf | while read
do
sysctl -w ${REPLY}
done
fi
sysctl -w kern.sysv.shmmax=4194304
sysctl -w kern.sysv.shmmin=1
[EMAIL PROTECTED]:31]~:1%sysctl kern.sysv.shmmax
kern.sysv.shmmax: 102400
It wouldn't surprise me at all if there was some other black magic at
work here. What I do know is that I had to comment out the sysctl line
in my /etc/rc to get that value to stick. I didn't make notes during my
testing
Damir Bijuklic <[EMAIL PROTECTED]> writes:
> My linux machine has following relevant locales:
> hr_HR
> hr_HR.iso88592
> hr_HR.utf8
> hrvatski
I'd recommend using hr_HR.utf8 plus UTF8 database encoding.
You'll need to re-initdb in order to install that as the
database locale :-(
"Nicolai Petri (lists)" <[EMAIL PROTECTED]> writes:
> It might still be a good idea for postgresql to be able to detect this
> collision without crashing each others backend or doing other weird stuff.
It tries --- see IpcSemaphoreCreate in src/backend/port/sysv_sema.c.
If the "jail" mechanism h
On 4/29/05, PABLO <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1639
> Logged by: PABLO
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.02
> Operating system: windows 2000
> Description:Problema re-instalacion
>
Damir Bijuklic <[EMAIL PROTECTED]> writes:
> I'm using WIN1250 locale on both databases.
Does your Linux platform even have such a locale? Mine doesn't.
("locale -a" will show you what is supported.) I suspect your
machine is not recognizing the LANG setting and is falling back
to behave as thou
Jim,
I didn't understand your comment
"It appears that you can shrink shmmax but not expand
it."
I did not comment out the kern.sysv.shmmax line and
it appears that my larger setting is sticking. Or is
it? What is that command to return the currrnt values
from the terminal?
Ted
--- "Jim C. N
You are correct - freebsd have indeed a global shm space which I don't think
is fixed in 5.x yet. We have run up to 4 postgresql in jails for our testing
and it just-works(tm) if we choose a different port for each database
instance.
It might still be a good idea for postgresql to be able to det
