Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1je1RI-0004k1-OY for pgsql-admin@arkaria.postgresql.org; Wed, 27 May 2020 19:10:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1je1RH-0001MS-Kh for pgsql-admin@arkaria.postgresql.org; Wed, 27 May 2020 19:10:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1je1RH-0001MG-DA; Wed, 27 May 2020 19:10:07 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1je1RD-00070t-QN; Wed, 27 May 2020 19:10:07 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0E61C5C00E5; Wed, 27 May 2020 15:10:02 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 27 May 2020 15:10:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=+ j1v/IjbEboxvelVKNBJeVkfnvWHkBUBiFVaWgYMKF8=; b=j4psKxIYTWA2peZrg Cdqv4GV7yJNh+L2TUzrGmFqunmwXJudqUqrju756qOufuPxtzGuNoBJcIEJ3n90E eiA6SqO+hGvjopQhjy0MbwzsKxPC4rdaDeUfhPWR7yVhhxYmoHq6h5i9grh0cSOq rY/YMq0g5id2lipkiVwn7uOEVuDjfEi6EQq7iRyuSHKKG8I84Es/XrhYttJMBr68 oRSDtrZ57rXW3B4tcb8Y2pOjypXAorHhhm9sSPc8JrK19vXGjkXieDvarWqiFAbB SOfpCLpcTsC6bmjaQzXKpq/ZEbnukNoxWn0huyujGOfPsFHIPvkHfAuBATDXhaNr +37Hg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=+j1v/IjbEboxvelVKNBJeVkfnvWHkBUBiFVaWgYMK F8=; b=hIl42MAg3gABPH35YQNKqQG7G8QThb7QJ8ahSS2aBPOQwR9uUM1W9GGZ8 jqDFXLw1zXt003VrxKILPJvqfpM7yquFGsg2Si58be4yVSv6NwUrOB8biAyQix4Y gSnUUFRdP7R8kEcASKPQUHtc83wU5a3FdOufDbR1SKJxeq5lt5S50TZ9N0xQZgNF 4pYH5r7cBVl5AsJhR9ZmZWeCBdUlZnZtogGnnFhyPyAN1PkRmqqysv+1cIuFUh7g KSuakLaDqwEs+sEZXqstnzFGgF8MHH4O2wjhum6WC87/4z0ucAY9JQg8uH0ml1T1 9riAh4e6v55+b41OtzJhF2vTQYP6w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddvgedguddvvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepveekffegudefgffhffejhfdtjeduhfevteeuieeg keegtdejvdefteeluddtveeinecuffhomhgrihhnpegtihhtuhhsuggrthgrrdgtohhmne cukfhppeejhedrudejvddrhedrvdefudenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrd gtohhm X-ME-Proxy: Received: from [192.168.1.3] (75-172-5-231.tukw.qwest.net [75.172.5.231]) by mail.messagingengine.com (Postfix) with ESMTPA id 1E4413280064; Wed, 27 May 2020 15:10:01 -0400 (EDT) Subject: Re: Suggest the Schedular for activities To: postgann2020 s , pgsql-admin , pgsql-general References: From: Adrian Klaver Message-ID: Date: Wed, 27 May 2020 12:10:00 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 5/27/20 9:06 AM, postgann2020 s wrote: > Hi Team, > > Thanks for your support. > > Currently, we are using tomcat for scheduling and want to replace it > with DB specific schedulers. > > Could someone please suggest the Schedular for application activities > instead of creating tomcat schedulers. > Also scheduler for DB specific activities as well instead of corn. Maybe?: https://www.citusdata.com/blog/2016/09/09/pgcron-run-periodic-jobs-in-postgres/ > > Thanks & Regards, > Postgann. -- Adrian Klaver adrian.klaver@aklaver.com