Qiang Wang wrote:
> We have PostgreSQL 8.3 running on Debian Linux server. We built an
> applicantion using PHP programming language and Postgres database. There are
> appoximatly 150 users using the software constantly. We had some performance
> degration before and after some studies we figured
] Will shared_buffers crash a server
Hei:
We have PostgreSQL 8.3 running on Debian Linux server. We built an
applicantion using PHP programming language and Postgres database. There
are appoximatly 150 users using the software constantly. We had some
performance degration before and after
On Fri, Apr 29, 2011 at 1:13 AM, Qiang Wang wrote:
>
> We have 10GB memory and we tuned PostgreSQL as follow:
> - max_connection = 100
> - work_mem = 50MB
You do know that work_mem is PER SORT right? Not per connection or
per user or per database. If all 100 of those connections needs to do
a
Normally under heavy load, a machine could potential stall, even seem to hang,
but not crash.
And judging from your description of the situation your only change was in
shared memory (IPC shm) usage, right?
I would advise to immediately run all sorts of (offline/online) hardware tests
(especiall
As for the question in the title, no, if the server starts, shared
buffers should not be the reason for a subsequent crash.
In debian, it is common that the maximum allowed shared memory setting
on your kernel will prevent a server from even starting, but I guess
that's not your problem (because i
Hei:
We have PostgreSQL 8.3 running on Debian Linux server. We built an applicantion
using PHP programming language and Postgres database. There are appoximatly 150
users using the software constantly. We had some performance degration before
and after some studies we figured out we will need
