Re: Self contradictory examining on rel's baserestrictinfo

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: ro b <bigbro_wq(at)hotmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Self contradictory examining on rel's baserestrictinfo
Date: 2024-11-27 16:09:15
Message-ID: CA+TgmoY8z9gp0=xF7nw0AFTK=U46cXNLYFmu=4B27RBe3_KwQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 27, 2024 at 10:28 AM ro b <bigbro_wq(at)hotmail(dot)com> wrote:
> I mean why can't draw the conclusions
> like the case a>1 and a>2 which can be simplified
> to a>2 if the operator > is btree opclass.

This question has already been discussed in some detail on this email
thread. First, we sometimes do detect it, as discussed by Peter.
Second, it is an unusual case and so not worth spending a lot of CPU
cycles to detect, as discussed by Tom.

We might still accept a patch to improve things in this area. For
example, if somebody could find a way to change the code so that we
are able to detect more cases without needing to spend more CPU
cycles, I think everyone would like that. However, that may be a
tricky goal to accomplish.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2024-11-27 16:11:45 Re: Statistics Import and Export
Previous Message Melanie Plageman 2024-11-27 16:08:01 Re: Make pg_stat_io view count IOs as bytes instead of blocks