From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Delete Enhancement Request
Date: Mon, 14 Jan 2019 10:08:45 -0600
Message-ID: <3f7591ea-9747-1ac6-4299-13fe66216ef2@gmail.com> (raw)
In-Reply-To: <EE8A78ED-B910-4FC0-BE85-39F74B90A055@illinois.edu>
References: <EE8A78ED-B910-4FC0-BE85-39F74B90A055@illinois.edu>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Delete Enhancement Request
In-Reply-To: <3f7591ea-9747-1ac6-4299-13fe66216ef2@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox