Hello,
I'm running the latest postgres version (9.2.3), and today for the first
time I encountered this:
12774 2013-04-02 18:13:10 CEST LOG: server process (PID 28463) was
terminated by signal 9: Killed
12774 2013-04-02 18:13:10 CEST DETAIL: Failed process was running:
BEGIN;declare "SQL_CUR0xf
Bert writes:
> I'm running the latest postgres version (9.2.3), and today for the first
> time I encountered this:
> 12774 2013-04-02 18:13:10 CEST LOG: server process (PID 28463) was
> terminated by signal 9: Killed
AFAIK there are only two possible sources of signal 9: a manual kill,
or the L
Hi Tom,
thanks for the tip! it was indeed the oom killer.
Is it wise to disable the oom killer? Or will the server really go down
withough postgres doing something about it?
currently I already lowered the shared_memory value a bit..
cheers,
Bert
On Tue, Apr 2, 2013 at 8:06 PM, Tom Lane wrot
Hi all,
I have turned vm.overcommit_memory on 1.
It's a pretty much dedicated machine anyway, except for some postgres
maintainance scripts I run in python / bash from the server.
We'll see what it gives.
cheers,
Bert
On Wed, Apr 3, 2013 at 8:45 AM, Bert wrote:
> Hi Tom,
>
> thanks for the
hi,
this is strange: one connection almost killed the server. So not a
combination of a lot of connections. I saw one connection grewing till over
100GB. Then I cancelled the connection before the oom killer became active
again.
These are my memory settings:
shared_buffers = 20GB
temp_buffers = 1
Bert writes:
> These are my memory settings:
> work_mem = 4GB
> How is it possible that one connection (query) uses all the ram? And how
> can I avoid it?
Uh ... don't do the above. work_mem is the allowed memory consumption
per query step, ie per hash or sort operation. A complex query can
ea
aha, ok. This was a setting pg_tune sugested. But I can understand how that
is a bad idea.
wkr,
Bert
On Thu, Apr 4, 2013 at 8:17 AM, Tom Lane wrote:
> Bert writes:
> > These are my memory settings:
> > work_mem = 4GB
>
> > How is it possible that one connection (query) uses all the ram? And h
