From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Documentation improvements for partitioning |
Date: | 2017-04-04 03:12:17 |
Message-ID: | CA+TgmoYPE5zpJ7FjSLg+k49S=PuM4bVH_JzLXPrWOqC4a=1Ssg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 3, 2017 at 12:52 AM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> I noticed what looks like a redundant line (or an incomplete sentence) in
> the paragraph about multi-column partition keys. In the following text:
>
> + partitioning, if desired. Of course, this will often result in a
> larger
> + number of partitions, each of which is individually smaller.
> + criteria. Using fewer columns may lead to coarser-grained
> + A query accessing the partitioned table will have
> + to scan fewer partitions if the conditions involve some or all of
> these
>
> This:
>
> + criteria. Using fewer columns may lead to coarser-grained
>
> looks redundant. But maybe we can keep that sentence by completing it,
> which the attached patch does as follows:
>
> + number of partitions, each of which is individually smaller. On the
> + other hand, using fewer columns may lead to a coarser-grained
> + partitioning criteria with smaller number of partitions.
>
> The patch also fixes some typos I noticed.
Thanks for the corrections. Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2017-04-04 03:26:58 | Re: Statement timeout behavior in extended queries |
Previous Message | Robert Haas | 2017-04-04 03:08:19 | Re: Fix obsolete comment in GetSnapshotData |