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

From Thom Brown
Subject Re: [pgadmin-hackers] Feature request: limited deletions
Date
Msg-id i2ibddc86151004080405vbdbe49c1t4dd9b5cf55ed5bc4@mail.gmail.com
Whole thread Raw
Responses Re: [pgadmin-hackers] Feature request: limited deletions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
<div class="gmail_quote">On 8 April 2010 11:55, Ian Barwick <span dir="ltr"><<a
href="mailto:barwick@gmail.com">barwick@gmail.com</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="margin:0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> 2010/4/8 Thom Brown
<<ahref="mailto:thombrown@gmail.com">thombrown@gmail.com</a>>:<br /><div class="im">> I couldn't find any
discussionon this, but the request is quite<br /> > straightforward.  Implement a LIMIT on DELETE statements like
SELECT<br/> > statements.<br /> ><br /> > So you could write:<br /> ><br /> > DELETE FROM massive_table
WHEREid < 40000000 LIMIT 10000;<br /> ><br /> > This would allow deletions in smaller batches rather than
waiting<br/> > potentially hours for the server to mark all those rows as deleted and<br /> > commit it as one
massivetransaction.<br /><br /></div>Is this a PgAdmin-specific question? If it is, apologies I am missing<br /> the
context.<br/><br /> If not, this is totally the wrong list, but why not use a subquery to<br /> control what is
deleted?<br/><font color="#888888"><br /><br /> Ian Barwick<br /></font></blockquote></div><br /> Erm... my mistake, I
thoughtthis was on the generic hackers list.  Moving it over in this reply.<br /><br /> Thom<br /> 

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remaining Streaming Replication Open Items
Next
From: Simon Riggs
Date:
Subject: Re: Hot Standby: Startup at shutdown checkpoint