Re: why partition pruning doesn't work?
От | Andrew Dunstan |
---|---|
Тема | Re: why partition pruning doesn't work? |
Дата | |
Msg-id | ff44c06f-bdd8-3433-a995-e9babb36088f@2ndQuadrant.com обсуждение исходный текст |
Ответ на | Re: why partition pruning doesn't work? (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
Ответы |
Re: why partition pruning doesn't work?
|
Список | pgsql-hackers |
On 06/12/2018 07:47 AM, Andrew Dunstan wrote: > > > On 06/11/2018 06:41 PM, Andrew Dunstan wrote: >> >> >> On 06/11/2018 06:24 PM, Tom Lane wrote: >>> >>> If we had any buildfarm critters running valgrind on >>> RELCACHE_FORCE_RELEASE or CLOBBER_CACHE_ALWAYS builds, they'd have >>> detected use of uninitialized memory here ... but I don't think we have >>> any. (The combination of valgrind and CCA would probably be too >>> slow to >>> be practical :-(, though maybe somebody with a fast machine could do >>> the other thing.) >>> >>> >> >> >> I don't have a fast machine, but I do have a slow machine already >> running valgrind and not doing much else :-) Let's see how lousyjack >> does with -DRELCACHE_FORCE_RELEASE >> >> > > > It added about 20% to the run time. That's tolerable, so I'll leave it > on. > > 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? cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: