Re: [pgadmin-hackers] Feature request: limited deletions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [pgadmin-hackers] Feature request: limited deletions
Date
Msg-id o2i603c8f071004080445w8971602br895805b5cbfbb44f@mail.gmail.com
Whole thread Raw
In response to Re: [pgadmin-hackers] Feature request: limited deletions  (Thom Brown <thombrown@gmail.com>)
Responses Re: [pgadmin-hackers] Feature request: limited deletions  (Csaba Nagy <ncslists@googlemail.com>)
List pgsql-hackers
On Thu, Apr 8, 2010 at 7:05 AM, Thom Brown <thombrown@gmail.com> wrote:
> On 8 April 2010 11:55, Ian Barwick <barwick@gmail.com> wrote:
>>
>> 2010/4/8 Thom Brown <thombrown@gmail.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?
>
> Erm... my mistake, I thought this was on the generic hackers list.  Moving
> it over in this reply.

I've certainly worked around the lack of this syntax more than once.
And I bet it's not even that hard to implement.

...Robert


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Remaining Streaming Replication Open Items
Next
From: Robert Haas
Date:
Subject: Re: Remaining Streaming Replication Open Items