Misestimate when applying condition like id = id - Mailing list pgsql-general

From Michael Lewis
Subject Misestimate when applying condition like id = id
Date
Msg-id CAHOFxGouAogS2oRKscsqzd2XVH+10n3w3ihxRngjRd-wC9gvTA@mail.gmail.com
Whole thread Raw
Responses Re: Misestimate when applying condition like id = id
List pgsql-general
Simplified example query-
explain
select * from organizations o where id = id;

On a PG10 instance I get-
Seq Scan on organizations o (cost=0.00..4.21 ***rows=1*** width=37)
Filter: (id = id)

On a PG11 instance with the same or very very similar data, I get-
Seq Scan on organizations o  (cost=0.00..5.70 ***rows=270*** width=37)
  Filter: (id IS NOT NULL)

Given this is a not null field, it translates to "is true" basically. The real query that this example was extracted from apparently had a typo in the join resulting in this bogus id = id condition, but I still curious about where this estimate change comes from.


Michael Lewis  |  Database Engineer
Entrata

pgsql-general by date:

Previous
From: Zahir Lalani
Date:
Subject: RE: Window functions speed
Next
From: Tom Lane
Date:
Subject: Re: Misestimate when applying condition like id = id