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 1sUp1C-005uVQ-Cw for pgsql-in-general@arkaria.postgresql.org; Fri, 19 Jul 2024 14:55:34 +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 1sUp1A-000c7x-IB for pgsql-in-general@arkaria.postgresql.org; Fri, 19 Jul 2024 14:55:32 +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 1sUp1A-000c7p-Ac for pgsql-in-general@lists.postgresql.org; Fri, 19 Jul 2024 14:55:32 +0000 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sUp17-000O5I-IU for pgsql-in-general@postgresql.org; Fri, 19 Jul 2024 14:55:31 +0000 Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-52e9c55febcso2460831e87.2 for ; Fri, 19 Jul 2024 07:55:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721400928; x=1722005728; darn=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=ShcKHYkzXFdA87ligputzqmqaUSQ4+lKhA1GA/S7GOg=; b=SfrC2CQv2Q0NL9JqQbObB3GoHIWBd6rwliFARKKPsJwJHSYK+kIxZCzGyP3NRVUHbM jy7zZMX95BG0k2mVP6U/DOttZ06X0FyUq9mDSeB9Zu0w+9zJ6/vTEpeTIcS3A/mly0v0 CmCGXUOfIPUX4CIuq6hgtAdkeUrcs86GMSdBhXnfwMwr4TUbH+MK06YRjTBvoLdwSNwl xMMcyKE4Wz3mcTvykh+nhi5dJkzRdQMmWd4jDyNT6EVVbzIR/i6aVtaktPrmHYVAJZMR /ipkYB1Mva8Cwp9X1O3/7sISn/0FQpzG6Npl4OEduz1AfgcpccUkuZ0XS1yWSKv5GhrL v3Xg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721400928; x=1722005728; 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=ShcKHYkzXFdA87ligputzqmqaUSQ4+lKhA1GA/S7GOg=; b=gCSWqksawFAYIEeMDDbCIrYYLx6F0MHpEJ2lji7coN0nlvZEQiFqemdsZ4OgAGGPHW W7AkYdeyRCrkNbSdqcykaqB4cEg0rdumAo3PA7DiVL61kOO+7XwV/mOWLXKFVI9T6USW YOoXBFV0kK5BlHlV4NtS361NIRIUGUee5wgIpzRpiBkHiS2otSZXqCG3gJncHSXX6XQh n33g5oSQotCygr86PEabZBFvCumUVMUna+/F0gvPtmn655fDp72Zy+Go5oIA6fxcrduq 6A7nyl8MPQf/o+mNMEOuDUyHtvS+jDkGyYvT0La/nsG8oN/PmLDdpbK5T8eQ6yS1Lewl Weqw== X-Forwarded-Encrypted: i=1; AJvYcCVtqWyHpBKO1BI07TQSdKHJcmqyU6AiInLqfjwXyCTFAdWil5QxCqJKjNLr/WaAVbyaUrF5rx9a9lXG2mX/s1H5vMRnC5Joqg614eOWJFuk X-Gm-Message-State: AOJu0Yxd+fedRhW2ULr07My5J4eT8ZCOe3PQ6Hw8VweIuxZrB2Eou8qJ nPvoNz6/kGgp8p3gnXt/auaMSZNjv2wNbKvBfIi+45YcsRkzd3/MvC/oOeX9cOYlDN3vHw1bVoc xggOfevOL/6b2gaU5kftsc6gUbsw= X-Google-Smtp-Source: AGHT+IFng5pc8mGt/0wWT1HMJcyvDkUMfc3SFvZHcBo6KpbQ3ewxb0rFQScRjJ2oPqFivzfxDWmTL6/9UTYm2kEPyF8= X-Received: by 2002:a05:6512:3b06:b0:52e:be14:7012 with SMTP id 2adb3069b0e04-52ee53d72a4mr6419969e87.32.1721400927623; Fri, 19 Jul 2024 07:55:27 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Durgamahesh Manne Date: Fri, 19 Jul 2024 20:26:37 +0530 Message-ID: Subject: Re: Fwd: Regarding tables detach concurrently with run_maintenance_proc() To: Christoph Berg , Durgamahesh Manne , pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000cea29d061d9ae257" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cea29d061d9ae257 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 19, 2024 at 7:55=E2=80=AFPM Christoph Berg wr= ote: > Re: Durgamahesh Manne > > with pg_partman By default proc() does not detach tables concurrently. > How > > do we implement tables detach concurrently without blocking other > sessions > > Here queries not using date column to detach tables with > > run_maintenance_proc() which is not using concurrently based on the > > retention policy which leads to scan all available child tables hence > need > > to trigger this proc with concurrently option to avoid blocking other > child > > tables beyond rentention policy while running statements on them > > You might have more success by filing pg_partman issues at > https://github.com/pgpartman/pg_partman/issues > > > Do we have any other alternative rather than using pg_partman()? > > Well you can just run the same commands manually that pg_partman would > run. > > Christoph > Hi You might have more success by filing pg_partman issues at https://github.com/pgpartman/pg_partman/issues >>> okay My intention is to have any other extension other than pg_partman to manage table partitions manually Regards Durga Mahesh --000000000000cea29d061d9ae257 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


Durga Mahesh
--000000000000cea29d061d9ae257--