Re: Is there any limit on the number of rows to import using copy command
| От | Ron Johnson |
|---|---|
| Тема | Re: Is there any limit on the number of rows to import using copy command |
| Дата | |
| Msg-id | CANzqJaDvu68fYz1tADA8=Gb=UV7asUYeyio6UnkcSgtr=F7uUQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Is there any limit on the number of rows to import using copy command ("sivapostgres@yahoo.com" <sivapostgres@yahoo.com>) |
| Список | pgsql-general |
On Thu, Jul 24, 2025 at 8:00 PM 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 86420 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.
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
В списке pgsql-general по дате отправления: