From: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Delete Enhancement Request |
Date: | 2019-01-14 15:18:20 |
Message-ID: | EE8A78ED-B910-4FC0-BE85-39F74B90A055@illinois.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
Thanks,
Lance Campbell
Web Services
University of Illinois
From | Date | Subject | |
---|---|---|---|
Next Message | Pepe TD Vo | 2019-01-14 15:24:48 | create tablespaces and users |
Previous Message | Bharat Telange | 2019-01-12 16:19:01 | Re: Monitoring tool |