Re: Simple DELETE on modest-size table runs 100% CPU forever - Mailing list pgsql-performance

From Michael Lewis
Subject Re: Simple DELETE on modest-size table runs 100% CPU forever
Date
Msg-id CAHOFxGp6LW+Eh=kUXKYu6YtL7n6jRB7rs29F7pPhA2VKucxfMw@mail.gmail.com
Whole thread Raw
In response to Simple DELETE on modest-size table runs 100% CPU forever  (Craig James <cjames@emolecules.com>)
List pgsql-performance
If I leave out the "analyze", here's what I get (note that the categories_staging_N table's name changes every time; it's
created on demand as "create table categories_staging_n(id integer)").

How/when are they created? In the same statement? After create, are you analyzing these tables? If not, the optimizer is blind and may be choosing a bad plan by chance.

pgsql-performance by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Simple DELETE on modest-size table runs 100% CPU forever
Next
From: Justin Pryzby
Date:
Subject: Re: Simple DELETE on modest-size table runs 100% CPU forever