Lists: | pgsql-admin |
---|
From: | "Eric L(dot) Blevins" <eblevins(at)insight(dot)rr(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Signal 11 |
Date: | 2002-10-31 06:15:00 |
Message-ID: | 002201c280a4$db201560$0201a8c0@Gateway |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-admin |
I'm fairly new to postgres, we are using postgresql-7.2.3 on Linux Red-Hat
8.0
I am having a problem with the shared buffers setting.
Whenever I set the shared buffers above 96 I start getting Segmentation
Faults
when performing queries.
However, if I leave the shared buffers set to 96 or lower the system
performs flawless.
I can start up postgres with up to 128Mb of shared buffers with no problems.
It just erratically faults.
Got any ideas?
Thanks!
Eric L. Blevins
From: | "Eric L(dot) Blevins" <eblevins(at)insight(dot)rr(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Signal 11 |
Date: | 2002-10-31 16:15:48 |
Message-ID: | 004901c280f8$ca2c97c0$0201a8c0@Gateway |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-admin |
From: "Andrew Sullivan" <andrew(at)libertyrms(dot)info>
To: "Eric L. Blevins" <eblevins(at)insight(dot)rr(dot)com>
Sent: Thursday, October 31, 2002 10:33 AM
Subject: Re: [ADMIN] Signal 11
>
> Have you checked your physical memory for flaws?
>
Yes, I have checked the memory, it is fine.
We had so much trouble we replaced the innards of the server.
New PS, MB, Processor, and RAM
Still have the exact same problem.
Could this possibly be related to some kernel setting?
Eric L. Blevins
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Eric L(dot) Blevins" <eblevins(at)insight(dot)rr(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Signal 11 |
Date: | 2002-10-31 16:21:25 |
Message-ID: | 7475.1036081285@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-admin |
"Eric L. Blevins" <eblevins(at)insight(dot)rr(dot)com> writes:
> From: "Andrew Sullivan" <andrew(at)libertyrms(dot)info>
>> Have you checked your physical memory for flaws?
>>
> Yes, I have checked the memory, it is fine.
I'd suggest checking harder ;-). I think an unreliable section of
memory is by far the most probable explanation. However, if you want
to dig for a software reason, try collecting stack backtraces from
the crashed processes' core dumps to see if there's any pattern.
regards, tom lane
From: | "Eric L(dot) Blevins" <eblevins(at)insight(dot)rr(dot)com> |
---|---|
To: | "Eric L(dot) Blevins" <eblevins(at)insight(dot)rr(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Signal 11 |
Date: | 2002-11-01 01:01:49 |
Message-ID: | 000e01c28142$451ba720$0201a8c0@Gateway |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-admin |
----- Original Message -----
From: "Eric L. Blevins" <eblevins(at)insight(dot)rr(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Sent: Thursday, October 31, 2002 11:15 AM
Subject: Re: [ADMIN] Signal 11
> From: "Andrew Sullivan" <andrew(at)libertyrms(dot)info>
> To: "Eric L. Blevins" <eblevins(at)insight(dot)rr(dot)com>
> Sent: Thursday, October 31, 2002 10:33 AM
> Subject: Re: [ADMIN] Signal 11
>
>
> >
> > Have you checked your physical memory for flaws?
> >
> Yes, I have checked the memory, it is fine.
> We had so much trouble we replaced the innards of the server.
> New PS, MB, Processor, and RAM
> Still have the exact same problem.
We got it working finally
1. We installed a kernel made for large memory machines from an RPM
2. in /etc/sysctl.conf
we added the following 3 lines
kernel.shmall = 805306368
kernel.shmmax = 805306368
kernel.shmmni = 8192
kernel.sem = 250 32000 100 128
3. In postgresql.conf
we set the shared_buffers to 50000
She is working flawless and very fast now.
Just the performance we needed!
Eric L. Blevins
www.wifimaps.com