Re: [PERFORM] Partitions and work_mem?

2014-11-16 Thread Magnus Hagander
On Oct 16, 2014 12:58 AM, "Tom Lane" wrote: > > Igor Neyman writes: > > From: Dave Johansen [mailto:davejohan...@gmail.com] > > This conversation has probably become a bit off topic, but my understanding is that what you're paying RedHat for is a stable platform for a long period of time. That me

Re: [PERFORM] pgtune + configurations with 9.3

2014-11-16 Thread Stuart Bishop
On 15 November 2014 06:00, Mark Kirkwood wrote: > It is probably time to revisit this 8GB limit with some benchmarking. We > don't really have a hard and fast rule that is known to be correct, and that > makes Alexey's job really difficult. Informally folk (including myself at > times) have sugge

Re: [PERFORM] Re[2]: [PERFORM] pgtune + configurations with 9.3

2014-11-16 Thread Stuart Bishop
On 15 November 2014 02:10, Alexey Vasiliev wrote: > Ok. Just need to know what think another developers about this - should > pgtune care about this case? Because I am not sure, what users with 512GB > will use pgtune. pgtune should certainly care about working with large amounts of RAM. Best

Re: [PERFORM] Partitions and work_mem?

2014-11-16 Thread Dave Johansen
On Wed, Oct 15, 2014 at 3:25 PM, Josh Berkus 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 th

Re: [PERFORM] Plan uses wrong index, preferring to scan pkey index instead

2014-11-16 Thread Tom Lane
Yuri Kunde Schlesner writes: > Does anyone know if there's any tweaking I can do in Postgres so that it > uses the appropriate plan? I suspect that the reason the planner likes the backlog_pkey is that it's almost perfectly correlated with table order, which greatly reduces the number of table fe