pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: rtroy@sciencetools.com
To: pgsql-docs@postgresql.org
Subject: Missing Adjective that's rather important
Date: Wed, 12 Apr 2017 17:39:38 +0000
Message-ID: <20170412173938.25941.6283@wrigleys.postgresql.org> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/9.6/static/ddl-partitioning.html
Description:

Hello,

I had somehow overlooked &quot;partitioning&quot; as a &quot;feature&quot; of Postgres, since
Postgres has always been capable of implementing partitions. But I stumbled
across this page while reviewing the latest feature list:

https://www.postgresql.org/docs/current/static/ddl-partitioning.html

The author apparently thinks there&#39;s only one kind of table partitioning,
but there are two, commonly known as &quot;horizontal&quot; and &quot;vertical&quot;. Horizontal
partitioning is what&#39;s discussed on that page and divides a table by the
value of some attribute (column) or collection of attributes. Vertical
partitioning, in contrast, divides up columns into different tables thus
requiring joins to &quot;reconstitute the table&quot;, also, of course, based upon
some attribute or collection of attributes.

Overall, it&#39;s a reasonable articulation, more of a how-to and
what-to-watch-out-for than a genuine discrete feature - presuming I read the
page correctly! However, if you&#39;re well aware of the distinction between
horizontal and vertical partitioning, the document reads rather awkwardly.

This can easily be resolved by the inclusion of the adjective &quot;horizontal&quot;
in front of &quot;partitioning&quot; in various places, especially in the first few
instances. 

I might point out that the whole page should be reviewed and some sections
re-written in light of the fact that Postgres has always supported both
horizontal and vertical partitioning through the traditional means, it&#39;s
just Postgres has features to help ease the implementation required to pull
it off, though that page only discusses horizontal partitioning, if I read
it correctly.

Vertical partitioning, of course, already has a lot of help through more
traditional means such as views. Perhaps a small line or three mentioning
vertical partitioning would be helpful for clarity.

I&#39;d be happy to take a stab at it if anyone wants, but it will have to wait
for May!

Regards,
Richard

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs


view thread (2+ messages)  latest in thread

Message-ID: <20170412173938.25941.6283@wrigleys.postgresql.org>
Permalink:  ../20170412173938.25941.6283@wrigleys.postgresql.org/
Also on:    postgresql.org/message-id/20170412173938.25941.6283@wrigleys.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: rtroy@sciencetools.com
  Subject: Re: Missing Adjective that's rather important
  In-Reply-To: <20170412173938.25941.6283@wrigleys.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox