| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Future directions for inheritance-hierarchy statistics |
| Date: | 2015-03-21 16:12:08 |
| Message-ID: | 550D9858.2020207@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/18/15 8:26 AM, Robert Haas wrote:
> In
> fact, EnterpriseDB has run into a number of customer situations where
> planning time even for non-inheritance queries is substantially higher
> than, shall we say, a competing commercial product.
If it's the commercial product I'm thinking of, they use multiple levels
of caching to avoid both parse costs as well as plan costs. It's always
impressed me that we didn't have to resort to such shenanigans, but
perhaps there's only so long we can avoid them.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2015-03-21 16:26:18 | Re: Remove fsync ON/OFF as a visible option? |
| Previous Message | Tom Lane | 2015-03-21 15:54:00 | Re: Remove fsync ON/OFF as a visible option? |