pgAgent commit: When multiple instances of pgAgent are running on the s

From: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: pgAgent commit: When multiple instances of pgAgent are running on the s
Date: 2017-10-24 15:04:48
Message-ID: E1e70l6-0004RM-Oy@gothos.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

When multiple instances of pgAgent are running on the same schema, only
one of the instance can pick up the job to run. Hence - rest of the
instances will never run the job. Hence - the job-thread does not
release the job object.

And, end up leaking the memory.

Releasing the job object from the destructor of the job-thread will
avoid such memory-leak.

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgagent.git;a=commitdiff;h=adc49f0a66eae645420f86acd383a75918771bf2
Author: Rob Emery <re-pgsql(at)codeweavers(dot)net>

Modified Files
--------------
job.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgadmin-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2017-10-24 15:05:05 Re: pgadmin4 l10n issues
Previous Message Ashesh Vashi 2017-10-24 15:00:37 Re: [pgAgent][Patch] Fixing connection pool leak