Re: Analyze all plans - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Analyze all plans
Date
Msg-id 25986.1548254799@sss.pgh.pa.us
Whole thread Raw
In response to Re: Analyze all plans  (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>)
Responses Re: Analyze all plans  (Donald Dong <xdong@csumb.edu>)
List pgsql-hackers
Oleksandr Shulgin <oleksandr.shulgin@zalando.de> writes:
> On Wed, Jan 23, 2019 at 9:44 AM Donald Dong <xdong@csumb.edu> wrote:
>> 1. Enumerate all the plans

> So enumerating all possible plans stops being practical for even slightly
> complicated queries.

Yes.  You can *not* disable the planner's aggressive pruning of losing
paths and subpaths without ending up with something that's completely
impractical for anything beyond toy queries.  That's just from the
standpoint of planner runtime.  Adding on the cost of actually creating
a finished plan and then running it for long enough to get a reliable
runtime for each case would ... well, let's just say you'd be safely dead
before you got any interesting answers.

            regards, tom lane


pgsql-hackers by date:

Previous
From: maayan mordehai
Date:
Subject: Re: postgres on a non-journaling filesystem
Next
From: Dmitry Dolgov
Date:
Subject: Re: ArchiveEntry optional arguments refactoring