From: | Olivier Gautherot <ogautherot(at)gautherot(dot)net> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Enhancement Request |
Date: | 2024-02-02 08:50:28 |
Message-ID: | CAJ7S9TWTE8ETq3MoTbXE-LFO8_+yAnJORZ9DKE=r-Pb2Ne5EhA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
El jue, 1 feb 2024 2:35, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> escribió:
> On Wed, Jan 31, 2024 at 3:51 PM Hajek, Nick <Nick(dot)Hajek(at)vishay(dot)com>
> wrote:
> [snip]
>
>> Delete from table1 where table1.id in (select table1.id from table1
>> limit yourlimitnumber)
>>
>
> The IN predicate is only efficient for a very small number of
> elements, supported by an index. People (including me) who would find
> DELETE FROM .. LIMIT TO ... useful want to delete a *lot* of rows (but not
> all in one giant statement).
>
Deleting large numbers of rows is a complex task with a lot of hidden
issues (index management between other things). Adding a LIMIT paradigm
will not simplify it in any way. I remember doing it on tables with over 50
millions rows and had my share of disaster recoveries. Partitions saved my
life.
Cheers
Olivier
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Lentes | 2024-02-02 09:31:45 | RE: Postgres alerting tools? |
Previous Message | Gabriel Guillem Barceló Soteras | 2024-02-02 07:10:44 | Re: Postgres alerting tools? |