pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedMissing Adjective that's rather important
2+ messages / 2 participants
[nested] [flat]
* Missing Adjective that's rather important
@ 2017-04-12 17:39 rtroy@sciencetools.com
2017-04-15 00:20 ` Re: Missing Adjective that's rather important Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 2+ messages in thread
From: rtroy@sciencetools.com @ 2017-04-12 17:39 UTC (permalink / raw)
To: pgsql-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 "partitioning" as a "feature" 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's only one kind of table partitioning,
but there are two, commonly known as "horizontal" and "vertical". Horizontal
partitioning is what'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 "reconstitute the table", also, of course, based upon
some attribute or collection of attributes.
Overall, it'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'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 "horizontal"
in front of "partitioning" 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'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'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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Missing Adjective that's rather important
2017-04-12 17:39 Missing Adjective that's rather important rtroy@sciencetools.com
@ 2017-04-15 00:20 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 2+ messages in thread
From: Peter Eisentraut @ 2017-04-15 00:20 UTC (permalink / raw)
To: rtroy@sciencetools.com; pgsql-docs
On 4/12/17 13:39, rtroy@sciencetools.com wrote:
> The author apparently thinks there's only one kind of table partitioning,
> but there are two, commonly known as "horizontal" and "vertical".
I think the unqualified term is pretty well understood to mean
horizontal partitioning.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2017-04-15 00:20 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-04-12 17:39 Missing Adjective that's rather important rtroy@sciencetools.com
2017-04-15 00:20 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
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