From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Alexander Farber <alexander(dot)farber(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Deleting takes days, should I add some index? |
Date: | 2020-11-27 15:05:12 |
Message-ID: | 20201127150512.GA21099@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2020-Nov-27, Alexander Farber wrote:
> Referenced by:
> TABLE "words_chat" CONSTRAINT "words_chat_gid_fkey" FOREIGN KEY (gid)
> REFERENCES words_games(gid) ON DELETE CASCADE
> TABLE "words_moves" CONSTRAINT "words_moves_gid_fkey" FOREIGN KEY (gid)
> REFERENCES words_games(gid) ON DELETE CASCADE
> TABLE "words_scores" CONSTRAINT "words_scores_gid_fkey" FOREIGN KEY
> (gid) REFERENCES words_games(gid) ON DELETE CASCADE
Make sure you have indexes on the gid columns of these tables. Delete
needs to scan them in order to find the rows that are cascaded to.
> So I ctrl-c (surprisingly not a single record was deleted; I was expecting
> at least some to be gone)
Ctrl-C aborts the transaction, so even though the rows are marked
deleted, they are so by an aborted transaction. Therefore they're
alive.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-11-27 15:11:11 | Re: How to debug authentication issues in Postgres |
Previous Message | Hemil Ruparel | 2020-11-27 15:01:50 | Re: How to debug authentication issues in Postgres |