[
https://issues.apache.org/jira/browse/MADLIB-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819837#comment-15819837
]
Nikolay S edited comment on MADLIB-1053 at 1/12/17 1:40 AM:
------------------------------------------------------------
Also, this problem tells us that MADlib (at least madpack) works with postgres
via command-line tool (psql) rather than via some libpq-based driver. I see
that you use `subprocess.Popen` in `run_query` function...
Did you consider using some Postgres driver for Python to execute SQL code? I
believe that driver would be better both in terms of performance and "clear
work" (no issues like this one, with psql's such startup messages)
was (Author: nikolays):
Also, this problem tells us that MADlib (at least madpack) works with postgres
via command-line tool (psql) rather than via some libpq-based driver. I see
that you use `subprocess.Popen` in `run_query` function...
Did you consider using some Python driver to execute SQL code? I believe that
driver would be better both in terms of performance and "clear work" (no issues
like this one, with psql's such startup messages)
> Cannot install having "\timing on" in .psqlrc
> ---------------------------------------------
>
> Key: MADLIB-1053
> URL: https://issues.apache.org/jira/browse/MADLIB-1053
> Project: Apache MADlib
> Issue Type: Bug
> Components: Madpack
> Reporter: Nikolay S
> Fix For: v1.10
>
>
> Actually subject speaks for itself: if you place smth like "\timing on" to
> .psqlrc (for convenience working with psql; smth that generates additional
> output at psql's startup time), you cannot install MADlib to some Postgres DB
> -- it reports:
> ```
> madpack.py : ERROR : Failed reading database version
> ```
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
