Claus Stadler <cstadler(at)informatik(dot)uni-leipzig(dot)de> writes:
> Query optimizer glitch: "...WHERE TRUE" condition in union results in
> bad query plan ...
Yeah, this is because a nonempty WHERE clause defeats simplifying the
UNION ALL into a simple "append relation" (cf is_safe_append_member()).
The planner will eventually figure out that WHERE TRUE is a no-op,
but that doesn't happen till later (and there are good reasons to do
things in that order).
Sooner or later I'd like to relax the restriction that appendrel members
can't have extra WHERE clauses, but don't hold your breath waiting...
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Rory Campbell-Lange||Date: 2012-03-04 09:58:38|
|Subject: Advice sought : new database server|
|Previous:||From: Claus Stadler||Date: 2012-03-03 22:43:17|
|Subject: ...WHERE TRUE" condition in union results in bad query pla|