[asterisk-bugs] [JIRA] (ASTERISK-28435) cdr_pgsql: Unix socket doesn't work
Kevin Harwell (JIRA)
noreply at issues.asterisk.org
Mon Jun 3 18:05:47 CDT 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247293#comment-247293 ]
Kevin Harwell commented on ASTERISK-28435:
------------------------------------------
Just a note, but we unfortunately we are unable to accept inline patches. A patch can either be submitted to gerrit directly, or attached here after signing the contributor's license agreement. For more information please see the following:
https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
> cdr_pgsql: Unix socket doesn't work
> -----------------------------------
>
> Key: ASTERISK-28435
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28435
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: CDR/cdr_pgsql
> Affects Versions: 16.3.0
> Reporter: Dmitry Svyatogorov
>
> After refactoring, function pgsql_reconnect() does "ast_str_set()" with statically composed string:
> {code}
> ast_str_set(&conn_info, 0, "host=%s port=%s dbname=%s user=%s"
> {code}
> It results in error while trying to connect to unix socket (empty host and port in config), so it's a regression.
> I propose the simple check:
> *<edit>*
> Editing to remove inline patch.
> Apologies, unfortunately inline patches are not allowed. Please see the patch contribution wiki [1] to learn more about contributing a patch to Asterisk, or attaching one here
> [1] https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
> *<end edit>*
> This patch works for me. _But m.b. there is more clear way?_
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list