Re: why doesn't optimizer can pull up where a > ( ... )

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: why doesn't optimizer can pull up where a > ( ... )
Date: 2019-11-20 13:19:32
Message-ID: 9C80C272-B3F0-4583-A9F7-62CF06FB72DC@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Nov 2019, at 13:15, Andy Fan <zhihui(dot)fan1213(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-11-20 13:54:11 Re: logical decoding : exceeded maxAllocatedDescs for .spill files
Previous Message Andy Fan 2019-11-20 12:16:33 Re: why doesn't optimizer can pull up where a > ( ... )