From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Ian Barwick <barwick(at)gmail(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Feature request: limited deletions |
Date: | 2010-04-08 11:05:11 |
Message-ID: | h2wbddc86151004080405iaf2652c7uc561c89336e2ede2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-hackers |
On 8 April 2010 11:55, Ian Barwick <barwick(at)gmail(dot)com> wrote:
> 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
>
Erm... my mistake, I thought this was on the generic hackers list. Moving
it over in this reply.
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-04-08 11:05:51 | Re: [pgadmin-hackers] Feature request: limited deletions |
Previous Message | Ian Barwick | 2010-04-08 10:55:30 | Re: Feature request: limited deletions |
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-04-08 11:05:51 | Re: [pgadmin-hackers] Feature request: limited deletions |
Previous Message | Robert Haas | 2010-04-08 10:58:39 | Re: Remaining Streaming Replication Open Items |