Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfuYL-00350X-48 for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Mar 2024 04:31:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rfuYI-00AzvE-I9 for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Mar 2024 04:31:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfuYI-00Azuw-37 for pgsql-bugs@lists.postgresql.org; Fri, 01 Mar 2024 04:31:18 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rfuYD-002CJ2-5M for pgsql-bugs@lists.postgresql.org; Fri, 01 Mar 2024 04:31:17 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-dcc71031680so1637151276.2 for ; Thu, 29 Feb 2024 20:31:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1709267471; x=1709872271; darn=lists.postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=almk6R99CP9tJ3i1pCOczZunhy+hHCZbNkejW/rIQl8=; b=gAMLlJgeuwUhZKOmZU33vqI1cqwD+8l+Se6Gnf9GzR/oG9zMefEWUYwf0SVfc6CZTt Dq+cmSHp/8G/cpbEXfMnpRGmTPBaq9WWlXobto0WhZbv1T/c3VA1gmVdiA75Aokn4otQ Js2rVSpuOimEKw1txO+1yfPjTTlqD8X7bMCaY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709267471; x=1709872271; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=almk6R99CP9tJ3i1pCOczZunhy+hHCZbNkejW/rIQl8=; b=bRtWSASU3SEGRliy2HDi84Rs6Ycqb3ONvPPZOgkCRIELmL2KmO+AjxgRpFWYUNBqx/ k+FEL7AsyFqvlchC7EjAqsFvq5MezePyE6+C+3rOmdunoQxoqr4qcK4S5+4Cb0jshv5k ZnZfxsj/4B4zIUkISLALnCyTS2a9jjck/xGUB5ranwHSQAOq5p6rLKMESO9sshMu5M09 Xh6J0ur3l9hXE19DDdGwu/Mg80EodYkkXP05pWSJAKhhmifwzk7CsHj+Ejmqs3GD5nxy bm7D4w3+3vfVlRZPAw9gwErVXMe4if3jv94QeMTcflGnY50xfEQz8uyrWIRnEbrSUr3t hcUw== X-Gm-Message-State: AOJu0YzJOhLxyEtMbJ9fZpxNbqnwwU97pSbmNmfHJ0YK1Ks9dkkVcQAy 0T/0g5LvILP5z524OD5QgRF+nnsdsUGgWTgtveYUsaTIu3WInFrn7hVTei+wMg== X-Google-Smtp-Source: AGHT+IHxTBOtESeIvjH7baQxcz7GjhG0MO2vFvaFPnqr+OR3q9Jvmcd354FC9DL6acdseTvbWxbnHA== X-Received: by 2002:a25:aca4:0:b0:dc7:4639:55d1 with SMTP id x36-20020a25aca4000000b00dc7463955d1mr469534ybi.18.1709267470938; Thu, 29 Feb 2024 20:31:10 -0800 (PST) Received: from rfd.leadboat.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id g13-20020a25ae4d000000b00dc74258241fsm667402ybe.45.2024.02.29.20.31.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Feb 2024 20:31:10 -0800 (PST) Date: Thu, 29 Feb 2024 20:31:08 -0800 From: Noah Misch To: Ramya Ashwin Cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: Facing issue in installing pg_cron extension in Postgresql 15 Message-ID: <20240301043108.63@rfd.leadboat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Feb 29, 2024 at 11:19:19AM +0000, Ramya Ashwin wrote: > I need to run a job which schedule everyday at midnight and for that am > trying to add pg_cron extension in Postgresql 15. I followed the > instructions and updated the postgresql.conf from the data directory. Ater > that it is recommended to restart the DB inorder to get all the > configurations implemented. This mailing list is for bugs in core PostgreSQL. pg_cron is out of scope. You could try https://github.com/citusdata/pg_cron/issues. > When I restated the Postgresql, it stopped and couldn't able to restart and > leads to reinstalling the same. When "it stopped and couldn't able to restart", there must have been associated log messages. Wherever you post, do share the exact log messages that led to your conclusions. > Please help to do the pg_cron installation without restarting the DB. https://github.com/citusdata/pg_cron#setting-up-pg_cron does require changing shared_preload_libraries, which requires a restart. If you haven't already done that, there's no supported way to avoid a restart.