Adrian Klaver <adrian.klaver@xxxxxxxxxxx> writes: > SET enable_indexscan=off; > EXPLAIN ANALYZE DELETE query > SET enable_indexscan=on; Note that you'd probably best do this in a fresh session, since the supposed problem is being tickled by a foreign-key check. I think the plans for those get cached, so if you'd already tried the same case earlier in the session, changing enable_indexscan wouldn't change the plan used. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
