Radovan Jablonovsky <radovan(dot)jablonovsky(at)replicon(dot)com> wrote:
> We are running PostgreSQL version 9.1.1
You should apply the latest bug fixes by updating to 9.1.4.
> with 32GB of RAM, 32GB of SWAP and during high load we could reach
> (swap + RAM) memory limit.
If you're even *starting* to swap you're doing something wrong, much
less exhausting swap space equal to actual RAM. What is your
While it's probably a good idea to configure the OOM killer to
behave more sanely, we tend to ignore it in favor of ensuring that
it never comes into play. We run about 200 databases 24/7 and I
think I've seen it kick in about twice -- when we ran queries that
leaked memory on each row in a big query.
In response to
pgsql-admin by date
|Next:||From: Ascarabina||Date: 2012-08-01 19:05:30|
|Subject: Re: Could You help me|
|Previous:||From: Gary Webster||Date: 2012-08-01 15:43:24|
|Subject: [pgsql] How bad is this full vacuum error?|