Re: pgagent errors on application_name
On Wed, Jul 8, 2015 at 7:06 AM, Josh Berkus <josh@agliodbs.com> wrote:
On 07/06/2015 08:52 PM, Ashesh Vashi wrote:
> Hi Josh,
>
> On Mon, Jul 6, 2015 at 11:55 PM, Josh Berkus <josh@agliodbs.com
> <mailto:josh@agliodbs.com>> wrote:
>
> To wit:
>
> postgres@9c7b33848038:~$ pgagent -l pgagent.log -f dbname=postgres
> user=postgres application_name=pgagent
> ERROR: Primary connection string is not valid!
> 18:15:15: Debug: In file ../src/unix/threadpsx.cpp at line 261:
> 'pthread_mutex_destroy()' failed with error 0x00000010 (Device or
> resource busy).
>
> Can you please check, which libpq it is using? (You may use /ldd/ for
> checking that.)
> The error suggests that It might be using very old version of libpq.
Nope, that's not the issue:
libpq.so.5 => /usr/lib/x86_64-linux-gnu/libpq.so.5 (0x00007fa7f377b000)
Note that the error message doesn't match the standard libpq error in
any case.
Yes - I missed that.
application_name in connection string is supported by pgAgent.
В списке pgadmin-support по дате отправления: