MIME-Version: 1.0
From: Lok P <loknath.73@gmail.com>
Date: Fri, 6 Sep 2024 01:44:00 +0530
Message-ID: <CAKna9VaVsDzfOfOGu1+grStp9BBHFMKrH5DCEbbtGcQUWJ74KQ@mail.gmail.com>
Subject: Faster data load
To: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000001bc936062164efbb"
Archived-At: <https://www.postgresql.org/message-id/CAKna9VaVsDzfOfOGu1%2BgrStp9BBHFMKrH5DCEbbtGcQUWJ74KQ%40mail.gmail.com>
Precedence: bulk

--0000000000001bc936062164efbb
Content-Type: text/plain; charset="UTF-8"

Hi,

We are having a requirement to create approx 50 billion rows in a partition
table(~1 billion rows per partition, 200+gb size daily partitions) for a
performance test. We are currently using ' insert into <target
table_partition> select.. From <source_table_partition> or <some
transformed query>;' method . We have dropped all indexes and constraints
First and then doing the load. Still it's taking 2-3 hours to populate one
partition. Is there a faster way to achieve this?

Few teammate suggesting to use copy command and use file load instead,
which will be faster. So I wanted to understand, how different things it
does behind the scenes as compared to insert as select command? As because
it only deals with sql engine only.

Additionally, when we were trying to create indexes post data load on one
partition, it took 30+ minutes. Any possible way to make it faster?

Is there any way to drive the above things in parallel by utilizing full
database resources?

It's postgres 15.4

Regards
Lok

--0000000000001bc936062164efbb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi,=C2=A0<div dir=3D"auto"><br><div dir=3D"auto">We are h=
aving a requirement to create approx 50 billion rows in a partition table(~=
1 billion rows per partition, 200+gb size daily partitions) for a performan=
ce test. We are currently using &#39; insert into &lt;target table_partitio=
n&gt; select.. From &lt;source_table_partition&gt; or &lt;some transformed =
query&gt;;&#39; method . We have dropped all indexes and constraints First =
and then doing the load. Still it&#39;s taking 2-3 hours to populate one pa=
rtition. Is there a faster way to achieve this?=C2=A0<div dir=3D"auto"><br>=
</div><div dir=3D"auto">Few teammate suggesting to use  copy command and us=
e file load instead, which will be faster. So I wanted to understand, how d=
ifferent things it does behind the scenes as compared to insert as select c=
ommand? As because it only deals with sql engine only.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Additionally, when we were trying to =
create indexes post data load on one partition, it took 30+ minutes. Any po=
ssible way to make it faster?=C2=A0</div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Is there any way to drive the above things in parallel by utili=
zing full database resources?</div><div dir=3D"auto"><br></div><div dir=3D"=
auto">It&#39;s postgres 15.4</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">Regards</div><div dir=3D"auto">Lok</div></div></div></div>

--0000000000001bc936062164efbb--