pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <david.rowley@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: why partition pruning doesn't work?
Date: Fri, 15 Jun 2018 10:25:27 -0400
Message-ID: <5d746bd9-8a79-93c8-885e-f005f7bd06df@2ndQuadrant.com> (raw)
In-Reply-To: <23131.1529071325@sss.pgh.pa.us>
References: <CAFj8pRBjrufA3ocDm8o4LPGNye9Y+pm1b9kCwode4X04CULG3g@mail.gmail.com>
	<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>
	<23131.1529071325@sss.pgh.pa.us>



On 06/15/2018 10:02 AM, Tom Lane wrote:
> 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.
>
> 			


OK.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (72+ messages)  latest in thread

Message-ID: <5d746bd9-8a79-93c8-885e-f005f7bd06df@2ndQuadrant.com>
Permalink:  ../5d746bd9-8a79-93c8-885e-f005f7bd06df@2ndQuadrant.com/
Also on:    postgresql.org/message-id/5d746bd9-8a79-93c8-885e-f005f7bd06df@2ndQuadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andrew.dunstan@2ndquadrant.com, tgl@sss.pgh.pa.us, david.rowley@2ndquadrant.com, Langote_Amit_f8@lab.ntt.co.jp, 9erthalion6@gmail.com, jeff.janes@gmail.com, ashutosh.bapat@enterprisedb.com, pavel.stehule@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: why partition pruning doesn't work?
  In-Reply-To: <5d746bd9-8a79-93c8-885e-f005f7bd06df@2ndQuadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox