Re: why doesn't optimizer can pull up where a > ( ... ) - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: why doesn't optimizer can pull up where a > ( ... )
Date
Msg-id 9C80C272-B3F0-4583-A9F7-62CF06FB72DC@yesql.se
Whole thread Raw
In response to why doesn't optimizer can pull up where a > ( ... )  (Andy Fan <zhihui.fan1213@gmail.com>)
Responses Re: why doesn't optimizer can pull up where a > ( ... )  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 20 Nov 2019, at 13:15, Andy Fan <zhihui.fan1213@gmail.com> wrote:

> 2.  why pg can't do it,  while greenplum can? 

It's worth noting that Greenplum, the example you're referring to, is using a
completely different query planner, and different planners have different
characteristics and capabilities.

cheers ./daniel



pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: why doesn't optimizer can pull up where a > ( ... )
Next
From: Alvaro Herrera
Date:
Subject: Re: logical decoding : exceeded maxAllocatedDescs for .spill files