| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Subject: | Re: Performance issue in foreign-key-aware join estimation |
| Date: | 2019-02-21 02:05:14 |
| Message-ID: | CAKJS1f99nES0YdtLPEz30VNFxxZwArdhJ+c+51UWxSETuitPMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg와이즈 토토SQL |
On Thu, 21 Feb 2019 at 15:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Pushed that one. I'm interested by the "POC" patch, but I agree
> that it'd take some research to show that it isn't a net negative
> for simple queries. It sounds like you're not really interested
> in pursuing that right now?
Thanks for pushing it.
I'm still interested in the POC patch. I just knew it wasn't something
for the back branches and thought something that was would be more
important... Things having gone quiet here wasn't a good source of
inspiration to do any further work on it. It's good to hear you're
interested.
> Anyway, I rebased the POC patch up to HEAD, just in case anyone
> still wants to play with it.
Cool. Thanks.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-21 02:11:06 | Re: NOT IN subquery optimization |
| Previous Message | Tom Lane | 2019-02-21 02:00:33 | Re: Performance issue in foreign-key-aware join estimation |