Re: Partitions and work_mem?

From: Dave Johansen <davejohansen(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Igor Neyman <ineyman(at)perceptron(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Partitions and work_mem?
Date: 2014-11-16 22:25:45
Message-ID: CAAcYxUeJx5kji-Xy7uR4AC4ZZK99dVcQ+whsYs6bch_JvgEtbQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Oct 15, 2014 at 3:25 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:

> On 10/15/2014 01:19 PM, Dave Johansen wrote:
> > Sorry I don't understand what you mean by that. My understanding is that
> > RedHat maintains fixes for security and other major issues for packages
> > that have been EOLed. Are you implying that that's not the case? Or
> > something else?
>
> RH probably backpatches our fixes as they come out. They did in the
> past, anyway.
>
> I just had the impression from your original post that this was a new
> system; if so, it would make sense to build it on a version of Postgres
> which wasn't already EOL.
>

Sorry for not being more clear in the original post. This is a system that
has been running for just over a year and the beta for RHEL 7 hadn't even
been released when we started things so 8.4 was the only real option.

Having said all of that, we recently had an increase in the number of users
and we had experienced database restarts because the Linux Out of Memory
Killer would kill a query on occassion. I just wanted to make sure that the
changes we were making were based on sound logic and we wouldn't be
experiencing these restarts anymore.

Thanks everyone for the help,
Dave

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Stuart Bishop 2014-11-17 04:52:45 Re: Re[2]: [PERFORM] pgtune + configurations with 9.3
Previous Message Tom Lane 2014-11-16 17:18:46 Re: Plan uses wrong index, preferring to scan pkey index instead