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 1sFyrw-0080Rq-LG for pgsql-general@arkaria.postgresql.org; Sat, 08 Jun 2024 16:24:41 +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 1sFyqv-000Bfw-Ps for pgsql-general@arkaria.postgresql.org; Sat, 08 Jun 2024 16:23:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFyqv-000Bfo-C4 for pgsql-general@lists.postgresql.org; Sat, 08 Jun 2024 16:23:38 +0000 Received: from mail-oa1-x33.google.com ([2001:4860:4864:20::33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sFyqt-000KgL-K4 for pgsql-general@lists.postgresql.org; Sat, 08 Jun 2024 16:23:36 +0000 Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-254a9b89be2so142499fac.2 for ; Sat, 08 Jun 2024 09:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717863814; x=1718468614; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=5RPLClAta89pD40AcTQyhXr+h17FMbo4/QN9Ev8Jdmo=; b=KjqKzcjSAVGiPtNxuDRdNirjuQGHdvCW70rYGFsmgNvVDtlOaC8PEKDH6vnYJGnbaG 3+PWowohgolTis5IlKNAcdJM8HpE8OgzAP0wUXH2QIfDzVMgsmLyLLqGI+buNu52RPNK UYZm1a0yLWOMNMocpEsoWoqP4timXX8Or7P2tbipj3vgyI60PrSM6/q2fYdhqNTQSpYY JdUB9y08keosibpEWITn0jMFDLy3TQ4FzAOfW7aqd0tSNn3EdMexE81fLyuaTL1GaJ0r HQjGE0MPy+QXP4HklgnlRi/xcwpojLGE3rPvyFw2khRJ5aDb0p95sIyVmIxPE5JXmdni ZFLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717863814; x=1718468614; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=5RPLClAta89pD40AcTQyhXr+h17FMbo4/QN9Ev8Jdmo=; b=T9NmrdLV0vcvyNPjjHrdD+DUk+34RBwGhiQKcedTAubn0GZNjFE5AL/0mkigUYXHMS 6k11gfJLKtk4MlB2eyeY/m2pxYQ72nfNlcjsTCDnY5r5pH2OtTqSIgVX/xbCuoHknRjI cSadXlRUwicteJicDmBIXzuXmJE3zyY/Bz0jtvpXS81psNiXHeIwmN/OvlIT1286xQwp mALt0Gq4CKRMcxkIcJZcoYV7HLxxt1dqM/MEFH35gd10LvLKezC8NXSDlsu1xbHMWP85 rVpJ2BKDC3T1gYJZVKNLQ+vabfFnfk13L5dppIDmaoqgfkuX96XWR56Gwt+/r1abtqzV jKEw== X-Gm-Message-State: AOJu0YzulISeleBQ6jbRpucd3PHcE5QUGznKhT2lpA5Hl7/8rmomVae1 TRpI6x8g3wpxZpYvvUDRExgsYLJ31mWKj+msOSz5Gs/tDavlPi7zl3a9Y90aJWjaCnQre6hQKLM xvfaSDSnRr3ExuUzR7BQ2udStuziL5w== X-Google-Smtp-Source: AGHT+IG9FOP3RKvbpnMZtjVKZ3QrtzCcF3c9+O/7bWxYvwVEGSZqO5mr/X92uyh+giWYeTi+YdTs0UYNTFQOl89Se3s= X-Received: by 2002:a05:6870:3509:b0:254:a778:6fbd with SMTP id 586e51a60fabf-254a778f6demr974955fac.6.1717863814355; Sat, 08 Jun 2024 09:23:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sat, 8 Jun 2024 12:23:22 -0400 Message-ID: Subject: Re: Question on pg_cron To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000006d629c061a635653" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006d629c061a635653 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jun 8, 2024 at 5:31=E2=80=AFAM yudhi s wrote: > Hello All, > > We have around 10 different partition tables for which the partition > maintenance is done using pg_partman extension. These tables have foreign > key dependency between them. We just called partman.run_maintanance_proc= () > through pg_cron without any parameters and it was working fine. So we can > see only one entry in the cron.job table. And it runs daily once. > > It was all working fine and we were seeing the historical partition being > dropped and new partitions being created without any issue. But suddenly = we > started seeing, its getting failed with error "ERROR: can not drop > schema1.tab1_part_p2023_12_01 because other objects depend on it" > Have you changed version lately of PG, pg_cron or pg_partman? Or maybe what pg_cron or pg_partman depends on? --0000000000006d629c061a635653 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jun 8, 2024 at 5:31=E2=80=AFAM yu= dhi s <learnerdatabase99@= gmail.com> wrote:
Hello All,

We = have around 10 different partition tables for which the partition maintenan= ce is done using pg_partman extension. These tables have foreign key depend= ency between them.=C2=A0 We just called partman.run_maintanance_proc() thro= ugh pg_cron without any parameters and it was working fine. So we can see o= nly one entry in the cron.job table. And it runs daily once.

It was = all working fine and we were seeing the historical partition being dropped = and new partitions being created without any issue. But suddenly we started= seeing, its getting failed with error "ERROR: can not drop schema1.ta= b1_part_p2023_12_01 because other objects depend on it"
=C2=A0
Have you changed version lately of PG, = pg_cron or pg_partman?=C2=A0 Or maybe what pg_cron or pg_partman depends on= ?
--0000000000006d629c061a635653--