|From:||David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>|
|To:||syluo1990(at)hotmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: BUG #15629: Typo in Documentation|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Mon, 11 Feb 2019 at 20:49, PG Bug reporting form
> 5.10.5. Partitioning and Constraint Exclusion
> Constraint exclusion is only applied during query planning; unlike partition
> pruning, it cannot be applied during query execution.
> Is it supposed to be "unlike partition pruning, it can be applied during
> query execution"?
That's a bit confusing. "it" looks like must have been intended to
reference constraint exclusion, but since partition pruning was
mentioned afterwards, then it makes more sense to apply it to that.
Maybe it would be more clear to write:
Constraint exclusion is only applied during query planning; unlike
partition pruning which can also be applied during query execution.
Small patch doing it that way is attached.
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
|Next Message||Sergei Kornilov||2019-02-11 09:55:19||Re: Error "new timeline 2 forked off current database system timeline" in cascaded replication, when master changes|
|Previous Message||Abhilash Mannathanil (amannath)||2019-02-11 05:57:24||Error "new timeline 2 forked off current database system timeline" in cascaded replication, when master changes|
|Next Message||Peter Eisentraut||2019-02-11 08:44:24||Re: Reporting script runtimes in pg_regress|
|Previous Message||David Rowley||2019-02-11 07:20:00||Re: pg_dump multi VALUES INSERT|