[
https://issues.apache.org/jira/browse/MADLIB-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842484#comment-17842484
]
Ed Espino commented on MADLIB-1518:
-----------------------------------
[~justatheory] : Apache MADlib's PGXN extension deviates from the typical
extension pattern and associated commands (such as load and unload). Based on
my understanding of the utility's {{madpack}} tool, it appears that the
extension primarily utilizes the PGXN client for retrieving and building the
package, relying on the {{pg_config}} available in the path, and installs by
default to {{{}/usr/local/madlib{}}}. Subsequently, it requires the user to
manually initiate the installation of the extension into the designated
PostgreSQL database using the {{madpack}} utility.
We could also bring this topic to the developer mailing list to see if anyone
can provide further insights into the current implementation.
> Files missing from PGXN Release
> -------------------------------
>
> Key: MADLIB-1518
> URL: https://issues.apache.org/jira/browse/MADLIB-1518
> Project: Apache MADlib
> Issue Type: Bug
> Reporter: David E. Wheeler
> Assignee: Ed Espino
> Priority: Major
> Attachments: MADlib-setup.out
>
>
> Starting with the 1.19.0 release, the PGXN distribution is missing most of
> its files. Compare:
> * [v1.18.0|https://api.pgxn.org/src/madlib/madlib-1.18.0/]
> * [v1.19.0|https://api.pgxn.org/src/madlib/madlib-1.19.0/]
> * [v1.20.0|https://api.pgxn.org/src/madlib/madlib-1.20.0/]
> This means users can no longer use the PGXN client to build and install
> madlib. Was this intentional?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
