Russell Smith wrote:
For the third time today, our server has crashed...
I would guess it's the linux OOM if you are running linux. You need to
turn off killing of processes when you run out of memory. Are you
getting close to running out of memory?
Good suggestion, it was a memory leak in an add-on library that we plug in to
the Postgres server.
OOM? Can you give me a quick pointer to what this acronym stands for and how I can
reconfigure it? It sounds like a "feature" old UNIX systems like SGI IRIX had,
where the system would allocate virtual memory that it didn't really have, then kill your
process if you tried to use it. I.e. malloc() would never return NULL even if swap space
was over allocated. Is this what you're talking about? Having this enabled on a server
is deadly for reliability.
Thanks,
Craig
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
