| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: why partition pruning doesn't work? |
| Date: | 2018-06-11 22:41:20 |
| Message-ID: | b91ddbe3-f45c-ec4f-3799-b5612f78bf38@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2018-06-11 23:00:27 | Re: [PATCH v18] GSSAPI encryption support |
| Previous Message | Andrew Dunstan | 2018-06-11 22:30:32 | Re: automating perl compile time checking |