Re: BUG #15629: Typo in Documentation - Mailing list pgsql-bugs

From Amit Langote
Subject Re: BUG #15629: Typo in Documentation
Date
Msg-id CA+HiwqG94pwK2uMo=CvewW82Y1D1q5qiP0nGm0wROqXNi+LDKw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15629: Typo in Documentation  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: Re: BUG #15629: Typo in Documentation
List pgsql-bugs
On Mon, Feb 11, 2019 at 5:25 PM David Rowley
<david.rowley@2ndquadrant.com> wrote:
> On Mon, 11 Feb 2019 at 20:49, PG Bug reporting form
> <noreply@postgresql.org> wrote:
> > https://www.postgresql.org/docs/current/ddl-partitioning.html
> >
> > 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.

+1

Maybe, the semicolon should be replaced by a comma?

Thanks,
Amit


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15630: Caused by: com.ibm.ws.extensionhelper.exception.iso-8859-1DatabaseException: Could not detect database
Next
From: PG Bug reporting form
Date:
Subject: BUG #15631: Generated as identity field in a temporary table with on commit drop corrupts system catalogs