[
https://issues.apache.org/jira/browse/MADLIB-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147960#comment-16147960
]
Frank McQuillan commented on MADLIB-1153:
-----------------------------------------
Hi Anthony,
It is because Greenplum database was forked from PostgreSQL in the 8.2 time
frame, a long time ago. Today we want to ensure that MADlib works on Greenplum
(and PostgreSQL and Apache HAWQ), so if users follow the 8.2 era aggregate
rules, then pivot will work for them on Greenplum data base. If you are
running on PostgreSQL, then you can use newer aggregate capability post 8.2.
Greenplum open source community is backporting features from later versions of
PostgreSQL to catch up, but that will take awhile.
Frank
> PostgreSQL version number in pivot
> ----------------------------------
>
> Key: MADLIB-1153
> URL: https://issues.apache.org/jira/browse/MADLIB-1153
> Project: Apache MADlib
> Issue Type: Documentation
> Components: Documentation
> Reporter: Anthony Nowocien
> Fix For: v1.12
>
>
> The links at the end of
> https://madlib.apache.org/docs/latest/group__grp__pivot.html all point out to
> PostgreSQL version 8.2, which has been EOL for almost 6 years as can be seen
> on https://www.postgresql.org/support/versioning/
> Those links could be replaced with the current version:
> https://www.postgresql.org/docs/current/static/functions-aggregate.html
> https://www.postgresql.org/docs/current/static/sql-createaggregate.html
> https://www.postgresql.org/docs/current/static/xaggr.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
