Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1fTpIv-00058z-M4
	for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Jun 2018 14:02:17 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1fTpIu-0003Bm-EQ
	for pgsql-hackers@arkaria.postgresql.org; Fri, 15 Jun 2018 14:02:16 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1fTpIu-0003Bd-78
	for pgsql-hackers@lists.postgresql.org; Fri, 15 Jun 2018 14:02:16 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1fTpIr-0007t4-69
	for pgsql-hackers@lists.postgresql.org; Fri, 15 Jun 2018 14:02:15 +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 w5FE25In023132;
	Fri, 15 Jun 2018 10:02:05 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
cc: David Rowley <david.rowley@2ndquadrant.com>,
        Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
        Dmitry Dolgov <9erthalion6@gmail.com>,
        Jeff Janes <jeff.janes@gmail.com>,
        Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>,
        Pavel Stehule <pavel.stehule@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: why partition pruning doesn't work?
In-reply-to: <ff44c06f-bdd8-3433-a995-e9babb36088f@2ndQuadrant.com>
References: 
 <CAFj8pRBjrufA3ocDm8o4LPGNye9Y+pm1b9kCwode4X04CULG3g@mail.gmail.com>
 <CA+q6zcVX9Gp0o06AXrozc0k4zkfera_wQiSyTkKXzgCsEqM6Yg@mail.gmail.com>
 <569483c5-a273-6537-1b5d-7a271ce439fb@lab.ntt.co.jp>
 <CAKJS1f9y_L-sXHwh74CGOoYcQRj8mDX9PnJqJLbpKujH1AS2ow@mail.gmail.com>
 <CAKJS1f-D1Tbi=Ozug7wfiZRf7wJs3tJ1G0cX5MK0nwstrc++tA@mail.gmail.com>
 <e6e751ea-0db4-0e7b-9513-97460edb60b3@lab.ntt.co.jp>
 <CAKJS1f_jatg5+qbrha2fGog63t3VdbNnOkYZitJtx-uo5H5EsQ@mail.gmail.com>
 <22805.1528386192@sss.pgh.pa.us>
 <CAKJS1f9xHoMntARi1RhqwAVZ-E0qp5a5f+Tf_chH9Vr8xOWiAw@mail.gmail.com>
 <21787.1528428171@sss.pgh.pa.us> <CAKJS1f9JMif8oCfM!
 SUQxmFEYmRSbpSvC7H99g1OaAZQSeBU5jA@mail.gmail.com>
 <6366.1528571895@sss.pgh.pa.us> <12624.1528578026@sss.pgh.pa.us>
 <CAKJS1f--wyKiJFS0WeGFFYT7Rz1Yy=zFLEaS6n=J-e9uzn61dA@mail.gmail.com>
 <26279.1528670981@sss.pgh.pa.us> <17850.1528755844@sss.pgh.pa.us>
 <b91ddbe3-f45c-ec4f-3799-b5612f78bf38@2ndQuadrant.com>
 <ba0c9a8d-61a8-b50b-6279-535174ac985b@2ndQuadrant.com> <ff44c06f-!
 bdd8-3433-a995-e9babb36088f@2ndQuadrant.com>
Comments: In-reply-to Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
	message dated "Fri, 15 Jun 2018 09:58:16 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <23130.1529071325.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Fri, 15 Jun 2018 10:02:05 -0400
Message-ID: <23131.1529071325@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> OK, lousyjack is back online with this, new and improved. It currently 
> takes 7.5 hours for a run.  Should I also add -DCATCACHE_FORCE_RELEASE?

I did some experimentation yesterday with valgrind plus both
RELCACHE_FORCE_RELEASE and CATCACHE_FORCE_RELEASE.  I didn't find
any new bugs, but adding CATCACHE_FORCE_RELEASE makes things quite
a lot slower :-(.  Not sure it's worth it.

			regards, tom lane