| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | amul sul <sulamul(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, David Steele <david(at)pgmasters(dot)net>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [POC] hash partitioning |
| Date: | 2017-05-25 15:13:25 |
| Message-ID: | CA+TgmoZ3sGz5gBNjiSY-6D1J729us53gv9PUGQmzUA4HNoSUMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 22, 2017 at 1:49 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> The prologue is arranged as one paragraph (with a new line) per
> member. Within each paragraph explanation for each partitioning
> strategy starts on its own line. One paragraph per member is more
> readable than separate paragraphs for each member and strategy.
The point is that you can either make it a separate paragraph or you
can make it a single paragraph, but you can't leave it halfway in
between. If it's one paragraph, every line should end at around the
80 character mark, without any short lines. If it's multiple
paragraphs, they should be separated by blank lines. The only line of
a paragraph that can be short is the last one.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-05-25 15:36:20 | Re: Server ignores contents of SASLInitialResponse |
| Previous Message | Sokolov Yura | 2017-05-25 15:12:44 | Re: Fix performance of generic atomics |