Re: Delete Enhancement Request

From: Paul Carlucci <paul(dot)carlucci(at)gmail(dot)com>
To: "Campbell, Lance" <lance(at)illinois(dot)edu>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Delete Enhancement Request
Date: 2019-01-15 00:50:18
Message-ID: CAKhGwmAqsSwy8uMTqrMtnwuBnedE8gZ-OmaOQpvSF6LsAHcm2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Do you mean like each row deleted is a separate transaction? The fact that
you canceled and only half had actually committed makes me say yes.

On Mon, Jan 14, 2019, 10:18 AM Campbell, Lance <lance(at)illinois(dot)edu 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.
>
>
>
> Thanks,
>
>
>
> Lance Campbell
>
> Web Services
>
> University of Illinois
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message David G. Johnston 2019-01-15 01:41:35 Re: Delete Enhancement Request
Previous Message Pepe TD Vo 2019-01-14 16:34:26 Re: create tablespaces and users