Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

chkpass

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    This case doesn't normally happen, because the planner usually clamps
    all row estimates to at least one row; but I found that it can arise
    when dealing with relations excluded by constraints.  Without a defense,
    estimate_num_groups() can return zero, which leads to divisions by zero
    inside the planner as well as assertion failures in the executor.
    
    An alternative fix would be to change set_dummy_rel_pathlist() to make
    the size estimate for a dummy relation 1 row instead of 0, but that seemed
    pretty ugly; and probably someday we'll want to drop the convention that
    the minimum rowcount estimate is 1 row.
    
    Back-patch to 8.4, as the problem can be demonstrated that far back.
    4ebbbf3c
    History
    Name Last commit Last update
    ..