Hello Again,
I've just tested the patch and the output is *much* more verbose with the same
set of flags now, even more so than the old version (see attached).
Thanks,
Rob
On 11/06/2018, Ashesh Vashi wrote:
> Hi Rob,
>
>
> On Mon, Jun 11, 2018 at 12:50 PM, Rob Emery
> w
was built and tested on Debian GNU/Linux 9.4 (stretch).
I've attached an example of the differing output when the dbname is missing
from the connectionstring; basically it's the same for all errors.
Many Thanks,
Rob
On 11/06/2018, Ashesh Vashi wrote:
> Hi Rob,
>
> On Sun,
Hi Guys,
I've been testing out PGAgent 4 (build today from master at commit
86ca5c5ed1ad572075ba27e05e4680ebdf5b9feb) to check the connection
handling on error is still fixed with the boost reimplementation
(which it is!)
and noticed a few issues compared to PGAgent 3 around feedback to the
user i
mitted your original patch.
>
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
> <http://www.enterprisedb.com/>
>
>
> *http://www.linkedin.com/in/asheshvashi*
> <http://www.linkedin.com/in/asheshvashi
ch is called in the
same place as the delete jt.
Is there a problem with chaining the ~JobThread() and ~Job() together as I
suggested previously? This does solve the leak.
Many Thanks,
Rob
On 23 October 2017 at 20:09, Rob Emery wrote:
> Hiya,
>
> I've just confirmed neither of these
this?
>>
>>
>> --
>>
>> Thanks & Regards,
>>
>> Ashesh Vashi
>> EnterpriseDB INDIA: Enterprise PostgreSQL Company
>> <http://www.enterprisedb.com>
>>
>>
>> *http://www.linkedin.com/in/asheshvashi*
&
--
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
> <http://www.enterprisedb.com>
>
>
> *http://www.linkedin.com/in/asheshvashi*
> <http://www.linkedin.com/in/asheshvashi>
>
> On Sat, Oct 21,
shvashi*
> <http://www.linkedin.com/in/asheshvashi>
>
> On Sat, Oct 21, 2017 at 8:36 PM, Rob Emery
> wrote:
>
>> Hi,
>>
>> Following on from https://www.postgresql.org/mes
>> sage-id/CA%2BOCxoz4tONxSpd1rdU-9SPKRzucz8Bar2CXkEDnCwV6H77Zy
>> A%40mail.gma
Hi,
Following on from
https://www.postgresql.org/message-id/CA%2BOCxoz4tONxSpd1rdU-9SPKRzucz8Bar2CXkEDnCwV6H77ZyA%40mail.gmail.com
I think I've identified and fixed the issue, please see the patch attached.
As I understand it when there are multiple pgagent instances and they clash
executing a j
