Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XeXWp-00076R-Dx for pgsql-performance@arkaria.postgresql.org; Wed, 15 Oct 2014 22:58:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XeXWo-0001GT-V0 for pgsql-performance@arkaria.postgresql.org; Wed, 15 Oct 2014 22:58:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XeXWn-0001GM-SW for pgsql-performance@postgresql.org; Wed, 15 Oct 2014 22:58:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XeXWj-00051U-RT for pgsql-performance@postgresql.org; Wed, 15 Oct 2014 22:58:44 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s9FMwEEU022718; Wed, 15 Oct 2014 18:58:14 -0400 From: Tom Lane To: Igor Neyman cc: Dave Johansen , Josh Berkus , pgsql-performance Subject: Re: Partitions and work_mem? In-reply-to: References: <543EAAA2.8010701@agliodbs.com> Comments: In-reply-to Igor Neyman message dated "Wed, 15 Oct 2014 21:00:21 -0000" Date: Wed, 15 Oct 2014 18:58:14 -0400 Message-ID: <22717.1413413894@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Igor Neyman writes: > From: Dave Johansen [mailto:davejohansen@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 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. > Let’s 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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance