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 1smQoM-005gQU-QT for pgsql-general@arkaria.postgresql.org; Fri, 06 Sep 2024 04:43:07 +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 1smQoL-006iN8-B0 for pgsql-general@arkaria.postgresql.org; Fri, 06 Sep 2024 04:43:05 +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 1smQoL-006iMz-00 for pgsql-general@lists.postgresql.org; Fri, 06 Sep 2024 04:43:05 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1smQoJ-000OUS-Dd for pgsql-general@lists.postgresql.org; Fri, 06 Sep 2024 04:43:04 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e1d2cf4cbf1so1256150276.1 for ; Thu, 05 Sep 2024 21:43:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725597782; x=1726202582; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ti9CBN46UEAEKvSVXh4j21M+Yh5ddmiPMrWl0N5wXSU=; b=gx9FJB8j46SiyusctakkVOQCNqVY4sh4/zjj8onAGD6yUOk4cTkbb7yHjsu69Vs484 ACYyeD0knu6m9kQpDPInLHYkc+oik2t7Dka1JK3DIpo3WEukis/8G1u9GmAPLWj7vam5 ZcZ6ABVakt67AXYzGRaJx9Fte4DzIwqyx9VwoIPO4hELYE7Wjo3SIitU72HpzlXsMWkN 4SafYZl+Ih8KjWn/rqu2WSTtM1oPOrYDxjxreWKrl3X20+n/8qK8V0tpBwDnkkWWzAg/ wYlqIjP5xJUGta9zfiIcz2FIFIzZZq7A94Ba+B40rmrXtcr7Eq3Rx6G6q48T7jd5q6xY 2deA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725597782; x=1726202582; h=cc: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=ti9CBN46UEAEKvSVXh4j21M+Yh5ddmiPMrWl0N5wXSU=; b=IE3ItAfQ6VFflaxTmFX/AEIUJFVmcnx7OkZfKvmOs4JXGMJOlOUxqyygadJy3Erlqs WWtHTVmftWktJgOw8vh4Cy0s69GCG84vVhIaxvgFurS//8WamxEiE2VK8V0xQnqgwXR1 G9Rj41NMMvVItj/JdQpxGDATbjpZXlJpcPMBjCJaWDTILN6LzZ32wNaxDXB6F/Hs0XzK G8zbFpzcyjIq1VK+CZjMOFOpd8f9FAcv5e5IjWDyvIGefecfAl0PJOr8pM9QQNlySNIC BjDT0tLyUxoCTAU55BP1n/UKxMMUbEacgwx/ivLOWVweTxpzKt1tIbEv6ukzeTHm07gC vF0A== X-Gm-Message-State: AOJu0YwJ+0MuUQaIUljl/IurQcqZrjqRJF1zpiwxcau8SUG5Y+HJ5zVP UrwcuPhsx3baGVNFPIMWCaDfNA5i4gnmeSSmc6SfHuugYjPqx4NW4Jt+p/HwktWyi2UOGinnwlf TrqpaT2uh4sVDFfDyY8yANUk/CsEbSw== X-Google-Smtp-Source: AGHT+IE03FkySLVaOaiiKhRo4CjN7DxIlqRtTrjwfffrFYF1r4k84dG4kJEMO79bMbian7PULk3CyLxhYJx2H2fmKDA= X-Received: by 2002:a05:6902:2083:b0:e1a:b3bb:b828 with SMTP id 3f1490d57ef6-e1d349c4566mr1505388276.34.1725597781829; Thu, 05 Sep 2024 21:43:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Lok P Date: Fri, 6 Sep 2024 10:12:49 +0530 Message-ID: Subject: Re: Faster data load To: Muhammad Usman Khan Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000cfb2d506216c0add" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cfb2d506216c0add Content-Type: text/plain; charset="UTF-8" On Fri, 6 Sept, 2024, 9:20 am Muhammad Usman Khan, wrote: > Hi, > > You can use pg_partman. If your table is partitioned, you can manage > partitions in parallel by distributing the load across partitions > concurrently. Or you can use citus. It can be an excellent solution, > especially for handling large data volumes and parallelizing data operations > Thank you. The tables are partitioned. Also during index creation we are trying to do it multiple partitions at same time from multiple sessions.But seeing out of memory error in 5th or 6th session. And even each sessions taking 30mins per partitions for index creation. Attach index partitions happening in seconds though. > > --000000000000cfb2d506216c0add Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Fri, 6 Sept, 2024,= 9:20 am Muhammad Usman Khan, <us= man.k@bitnine.net> wrote:
Hi,

You can use pg_part= man. If your table is partitioned, you can manage partitions in parallel by= distributing the load across partitions concurrently. Or you can use citus= . It can be an excellent solution, especially for handling large data volum= es and parallelizing data operations


Thank you.=C2=A0
The tables are p= artitioned. Also during index creation we are trying to do it multiple part= itions at same time from multiple sessions.But seeing out of memory error i= n 5th or 6th session. And even each sessions taking 30mins per partitions f= or index creation. Attach index partitions happening in seconds though.=C2= =A0

--000000000000cfb2d506216c0add--