MIME-Version: 1.0
References: <CANbhV-EuaLm4H3g0+BSTYHEGxJj3Kht0R+rJ8vT57Dejnh=_nA@mail.gmail.com>
 <CANbhV-HGhrkoF9BoHXScVZY8_HnBoHzGRQU15E6iPaF6ij0Cmw@mail.gmail.com>
 <91533bcd-c3a3-5844-7449-43aceede2117@enterprisedb.com> <CA+TgmoaGDw2baysiK+qqL+c3roa-9cPSvJ_Kwdgx7RoPQR0TaA@mail.gmail.com>
In-Reply-To: <CA+TgmoaGDw2baysiK+qqL+c3roa-9cPSvJ_Kwdgx7RoPQR0TaA@mail.gmail.com>
From: Simon Riggs <simon.riggs@enterprisedb.com>
Date: Thu, 10 Mar 2022 17:42:14 +0000
Message-ID: <CANbhV-HTc4=fK4tMb+1UPRLs4MYe9y21cxNbg9nHUGVZWbUBYA@mail.gmail.com>
Subject: Re: Parameter for planner estimate of recursive queries
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, 
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CANbhV-HTc4%3DfK4tMb%2B1UPRLs4MYe9y21cxNbg9nHUGVZWbUBYA%40mail.gmail.com>
Precedence: bulk

On Fri, 28 Jan 2022 at 14:07, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Tue, Jan 25, 2022 at 4:44 AM Peter Eisentraut
> <peter.eisentraut@enterprisedb.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/