| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parameter for planner estimate of recursive queries |
| Date: | 2022-03-10 17:42:14 |
| Message-ID: | CANbhV-HTc4=fK4tMb+1UPRLs4MYe9y21cxNbg9nHUGVZWbUBYA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 28 Jan 2022 at 14:07, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Tue, Jan 25, 2022 at 4:44 AM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> > On the one hand, this smells like a planner hint. But on the other
> > hand, it doesn't look like we will come up with proper graph-aware
> > selectivity estimation system any time soon, so just having all graph
> > OLTP queries suck until then because the planner hint is hardcoded
> > doesn't seem like a better solution. So I think this setting can be ok.
>
> I agree. It's a bit lame, but seems pretty harmless, and I can't see
> us realistically doing a lot better with any reasonable amount of
> work.
Shall I set this as Ready For Committer?
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2022-03-10 17:44:13 | Re: ltree_gist indexes broken after pg_upgrade from 12 to 13 |
| Previous Message | Robert Haas | 2022-03-10 17:32:08 | Re: pg_stat_statements and "IN" conditions |