From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Delete Enhancement Request |
Date: | 2019-01-14 16:08:45 |
Message-ID: | 3f7591ea-9747-1ac6-4299-13fe66216ef2@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 1/14/19 9:18 AM, Campbell, Lance wrote:
>
> Please consider adding this feature to PostgreSQL.
>
> Use Case:
>
> When deleting a large number of records with constraints and triggers
> PostgreSQL is exceptionally slow.
>
> Suggested change:
>
> I believe a way to speed this processes up would be to offer an option a
> user could “turn on” prior to doing the delete.
>
> Example: set delete-no-roll-back=true
>
> Now as PostgreSQL deletes rows it literally deletes them one at a time as
> though the user was only deleting a single row. This means that if cancel
> were executed on a delete action then it would only roll back the current
> row that PostgreSQL was in the process of deleting. Example: if you had
> 10 million row to delete and then pressed cancel after three minutes maybe
> 5 million are deleted.
>
You seem to be asking for an unlogged transaction, but that doesn't have
anything to do with efficiently deleting rows.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Pepe TD Vo | 2019-01-14 16:09:03 | Re: create tablespaces and users |
Previous Message | Shreeyansh Dba | 2019-01-14 15:46:37 | Re: create tablespaces and users |