Re: pgagent errors on application_name

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
Cc: pgadmin-support <pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgagent errors on application_name
Date: 2015-07-08 01:36:55
Message-ID: 559C7EB7.9030307@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On 07/06/2015 08:52 PM, Ashesh Vashi wrote:
> Hi Josh,
>
> On Mon, Jul 6, 2015 at 11:55 PM, Josh Berkus <josh(at)agliodbs(dot)com
> <mailto:josh(at)agliodbs(dot)com>> wrote:
>
> To wit:
>
> postgres(at)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.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Ashesh Vashi 2015-07-08 04:56:58 Re: pgagent errors on application_name
Previous Message mirza 2015-07-07 12:26:39 Windows 8 64 bit 4679 Char Problem