From: | Ian Barwick <barwick(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Feature request: limited deletions |
Date: | 2010-04-08 10:55:30 |
Message-ID: | o2h1d581afe1004080355i58f97865v5cf3c46d9b133208@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-hackers |
2010/4/8 Thom Brown <thombrown(at)gmail(dot)com>:
> I couldn't find any discussion on this, but the request is quite
> straightforward. Implement a LIMIT on DELETE statements like SELECT
> statements.
>
> So you could write:
>
> DELETE FROM massive_table WHERE id < 40000000 LIMIT 10000;
>
> This would allow deletions in smaller batches rather than waiting
> potentially hours for the server to mark all those rows as deleted and
> commit it as one massive transaction.
Is this a PgAdmin-specific question? If it is, apologies I am missing
the context.
If not, this is totally the wrong list, but why not use a subquery to
control what is deleted?
Ian Barwick
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-04-08 11:05:11 | Re: Feature request: limited deletions |
Previous Message | Thom Brown | 2010-04-08 10:06:18 | Feature request: limited deletions |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-04-08 10:57:16 | Re: A maze of twisty mailing lists all the same |
Previous Message | Heikki Linnakangas | 2010-04-08 10:33:31 | Re: Hot Standby: Startup at shutdown checkpoint |