MIME-Version: 1.0
References: <1453510076.1900935.1753260637232.ref@mail.yahoo.com>
 <1453510076.1900935.1753260637232@mail.yahoo.com> <CAHyXU0x1uW_349ONE+35KT87Ua-dX8-QaZ5Sj6eENTMwsX=okw@mail.gmail.com>
 <2129916799.2277829.1753359532611@mail.yahoo.com> <cd5ad7f0-9506-4828-9c13-88f34e8e4c8c@aklaver.com>
 <26359739.2491053.1753401573405@mail.yahoo.com>
In-Reply-To: <26359739.2491053.1753401573405@mail.yahoo.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 24 Jul 2025 20:41:34 -0400
Message-ID: <CANzqJaDvu68fYz1tADA8=Gb=UV7asUYeyio6UnkcSgtr=F7uUQ@mail.gmail.com>
Subject: Re: Is there any limit on the number of rows to import using copy command
To: Pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000d86edd063ab6347e"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaDvu68fYz1tADA8%3DGb%3DUV7asUYeyio6UnkcSgtr%3DF7uUQ%40mail.gmail.com>
Precedence: bulk

--000000000000d86edd063ab6347e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 24, 2025 at 8:00=E2=80=AFPM sivapostgres@yahoo.com <
sivapostgres@yahoo.com> wrote:
[snip]

> 3.  Regarding moving the logic to procedure.  Won't the trigger work?
> Will it be a burden for 86420 records?  It's working, if we insert few
> thousand records.  After split of trigger function, it's working for 8642=
0
> records.  Are triggers overhead for handling even 100000 records?
>

What causes the overhead when a trigger fires is all the work that it has
to do.

Thus, if the SELECT or UPDATE statements in the triggers do not have good
index support, then _that_ is what will slow down the trigger as the number
of records gets bigger.   Of course, the triggers are not slow, it's the
statements in the trigger that are slow.

Likewise, if there are many many indices on the tables, that will slow
things down too: more indices means more work!
Thus, drop as many indices as possible before loading data.


--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jul 24, 2025 at 8:00=E2=80=AFPM <=
a href=3D"mailto:sivapostgres@yahoo.com">sivapostgres@yahoo.com</a> &lt;<a =
href=3D"mailto:sivapostgres@yahoo.com">sivapostgres@yahoo.com</a>&gt; wrote=
:</div><div class=3D"gmail_quote gmail_quote_container"><div>[snip]=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style=3D"fo=
nt-family:&quot;times new roman&quot;,&quot;new york&quot;,times,serif;font=
-size:16px"><div dir=3D"ltr"></div><div dir=3D"ltr">3.=C2=A0 Regarding movi=
ng the logic to procedure.=C2=A0 Won&#39;t the trigger work?=C2=A0 Will it =
be a burden for 86420 records?=C2=A0 It&#39;s working, if we insert few tho=
usand records.=C2=A0 After split of trigger function, it&#39;s working for =
86420 records.=C2=A0 Are triggers overhead for handling even 100000 records=
?=C2=A0 </div></div></div></blockquote><div><br></div><div>What causes the =
overhead when a trigger fires is all the work that it has to do.</div><div>=
<br></div><div>Thus, if the SELECT or UPDATE statements in the triggers do =
not have good index support, then _that_ is what will slow down the trigger=
 as the number of records gets bigger.=C2=A0 =C2=A0Of course, the triggers =
are not slow, it&#39;s the statements in the trigger that are slow.</div><d=
iv><br></div><div>Likewise, if there are many many indices on the tables, t=
hat will slow things down too: more indices means more work!</div><div>Thus=
, drop as many indices as possible before loading data.</div><div><br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style=3D"font-=
family:&quot;times new roman&quot;,&quot;new york&quot;,times,serif;font-si=
ze:16px"><div dir=3D"ltr"></div></div></div></blockquote></div><div><br></d=
iv><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" cl=
ass=3D"gmail_signature"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and but=
ter sauce.<div>Don&#39;t boil me, I&#39;m still alive.<br><div><div>&lt;Red=
acted&gt; lobster!</div></div></div></div></div></div>

--000000000000d86edd063ab6347e--