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 1pyI5A-0007mw-4E for pgsql-general@arkaria.postgresql.org; Sun, 14 May 2023 20:12:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pyI58-00044V-Q6 for pgsql-general@arkaria.postgresql.org; Sun, 14 May 2023 20:12:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pyI57-00044K-6E for pgsql-general@lists.postgresql.org; Sun, 14 May 2023 20:12:38 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pyI51-002Kei-Pb for pgsql-general@lists.postgresql.org; Sun, 14 May 2023 20:12:35 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 41ED032009E9; Sun, 14 May 2023 16:12:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 14 May 2023 16:12:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1684095148; x=1684181548; bh=JlJkpcvCRvj68a3uVj8Hl/wZ87HLvSNJ7OJ 5iFgc+P8=; b=pnM6imG1w5yoh0iJthVCuwyLdwLWCpr5GohsEZcZ/qhhhwDKr9K QfachbuW5iklb7q01bVv9NY0YNG5D9gON6lMow0XVuZ8mLIXquXJkaOp7UJgbM7O DGZiloCZliBfv+SbmpJgs5+eUeZRSddepjf3UeWTLoi5qOtKnjjbicp15qC5J79R C2CG3wpOXosnDDXTQfCBa7eceWINJP1dHI4zVP6xL4VmFv4eowiot6bKQcnpucbI 40HC+IidYjEr3dRv7P7txsYCfjvttSV+AyAQ4y38fDV07A2GaGyZIXRtEhdOlzrx qnFmlDr7Oo0XuHRXVlX4TcXjHg2bWhCJ7rA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1684095148; x=1684181548; bh=JlJkpcvCRvj68a3uVj8Hl/wZ87HLvSNJ7OJ 5iFgc+P8=; b=PtNmd+DlSmE8gDACIn1LAeBluYxvGdkQ+bE7Gqt3olAdkU9F4oJ o5QtL83XEDKQVPOrwhfODG71NLkWion5Aqg4ppxaMvkj9UECMTRW+fBnl1ND+0K8 bB78aWlRrppKvj6kFNYAqjD+0TVR+Ho2rPZg9hM1wrx5Ej4jcxggKoLDcLp6J+9G 0gArRgOIFk0ytqH1+CmLyz6AxgCXS2S96Ur+Ym31bze/xPdtoatEzWOJhzpy4PYZ KYwqtqUlnHdgXviD9fLjPA/Sey4XikobjzByKehaW9hKxTOYZhhCMNNmum6pRm2V V1n3lV1ID5hGNV1AGQxJHwwk1OyLaao8l8g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeehhedgudegjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttdefjeenucfhrhhomheptegu rhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrd gtohhmqeenucggtffrrghtthgvrhhnpefhgeevkeefleffvdfgvdefffdtueejheehueei fffhfeeihfdvhffgtefgvdeugfenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorh hgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggu rhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 14 May 2023 16:12:27 -0400 (EDT) Message-ID: Date: Sun, 14 May 2023 13:12:27 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: PG_Cron - Error Message Connection failed To: =?UTF-8?Q?FOUTE_K=2e_Jaur=c3=a8s?= Cc: Fabricio Pedroso Jorge , PostgreSQL General References: <3b9c9577-8ff8-92f3-4e9f-6600770b938c@aklaver.com> <6dc19634-8441-b14e-5bb7-4491011da8df@aklaver.com> <390d91e2-762d-5a8e-97ac-a645dc0dc271@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/14/23 13:04, FOUTE K. Jaurès wrote: > > > Le dim. 14 mai 2023 à 16:12, Adrian Klaver > a écrit : > > Not what was requested. > > In the post linked to here: > > https://www.postgresql.org/message-id/CAHQ1jffWF7Y8c1X7EK3JvbLJgw1GEcVk0uPa3%2B0CJo4h8PFHVw%40mail.gmail.com > > there was an image of the result of: > > SELECT cron.schedule( 'TEST','30 seconds', $$SELECT 1$$); > > Provide that result as text. > > jobid |  schedule  | command  | nodename  | nodeport | >  database                  | username | active | jobname > -------+------------+----------+-----------+----------+--------------------------------------------+----------+--------+--------- >      8 | 30 seconds | SELECT 1 | localhost |     5692 | databasename | > postgres | t      | TEST > (1 row) That is not the same result as in the image, it had additional fields: runid, job_pid, status, return_message, start_time. Also the database field had not been edited. In the original image it looks like there was multiple databases named. From what I understand of pg_cron a job can only run on one database at a time. -- Adrian Klaver adrian.klaver@aklaver.com