Re: Partitions and work_mem?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Igor Neyman <ineyman(at)perceptron(dot)com>
Cc: Dave Johansen <davejohansen(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Partitions and work_mem?
Date: 2014-10-15 22:58:14
Message-ID: 22717.1413413894@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Igor Neyman <ineyman(at)perceptron(dot)com> writes:
> From: Dave Johansen [mailto:davejohansen(at)gmail(dot)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 means creating/backporting of fixes for security and other critical issues for packages that have been EOLed.
> Assuming the above is true, (which I beleve to be the case https://access.redhat.com/support/policy/updates/errata ), I don't see what would prevent RedHat from making a patch and applying it to the latest 8.4 release to resolve any newly discovered issues. Isn't that the whole point of open source and RedHat being able to do with the code what it wishes as long as it meets the requirements of the license? So are you claiming that RedHat doesn't/won't do this? Is incapable of doing this? Or am I missing something?

> Tom Lane is probably better authority on this issue.
> Lets wait and see what he says.

That is in fact exactly what people pay Red Hat to do, and it was my job
to do it for Postgres when I worked there. I don't work there any more,
but I'm sure my replacement is entirely capable of back-patching fixes as
needed.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Дмитрий Шалашов 2014-10-16 12:35:13 Partitioned tables and SELECT ... ORDER BY ... LIMIT
Previous Message Josh Berkus 2014-10-15 22:25:06 Re: Partitions and work_mem?