| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Delete Enhancement Request |
| Date: | 2019-01-15 01:41:35 |
| Message-ID: | CAKFQuwYCdDxwDh6yK98PLs3jewVb5zdDWE3J2sS-3qZh5KTEmg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Jan 14, 2019 at 8:18 AM Campbell, Lance <lance(at)illinois(dot)edu> wrote:
> Use Case:
> When deleting a large number of records with constraints and triggers PostgreSQL is exceptionally slow.
You may wish to provide an explicit situation that you are
experiencing so that others may offer their experienced insights as to
whether you could be doing anything different to increase the speed of
your deletes or techniques to batch them yourself.
I fail to comprehend how "ability to abort deleting mid-stream and not
lose any progress" is a solution to "deleting...is exceptionally slow"
- its more likely your proposed feature would increase the total time
spent performing the full delete.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-15 01:46:54 | Re: Delete Enhancement Request |
| Previous Message | Paul Carlucci | 2019-01-15 00:50:18 | Re: Delete Enhancement Request |