Re: a path towards replacing GEQO with something better

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: a path towards replacing GEQO with something better
Date: 2021-06-15 17:11:36
Message-ID: CA+Tgmoa07pD20XO35d8HCP=JPxiqt0ODFTKgKqExbk78gpOVkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 15, 2021 at 1:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Still, I take your point that maybe we could ratchet down the cost of
> exhaustive search by skimping on this part. Maybe it'd work to skip
> bushy so long as we'd found at least one left-deep or right-deep path
> for the current rel.

Yes, that sounds better.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-06-15 17:18:06 Re: unnesting multirange data types
Previous Message Peter Geoghegan 2021-06-15 17:10:42 Re: snapshot too old issues, first around wraparound and then more.