On Mon, 28 Mar 2005, Stephan Szabo wrote:
> > On Mon, 28 Mar 2005, Simon Riggs wrote:
> > > run the EXPLAIN after doing
> > > SET enable_seqscan = off
...
> I think you have to prepare with enable_seqscan=off, because it
> effects how the query is planned and prepared.
orfs=# SET enable_seqsca
> Well, based upon the evidence so far, the Optimizer got it right:
Agreed. So, this means that the answer to my original question is "that
delete gonna take a long time"?
Seems that there is still something wrong. From what I can tell from
everyones questions, the FK constraint on measurement is
> Each value has 1/13th of the table, which is too many rows per value to
> make an IndexScan an efficient way of deleting rows from the table.
But, the original question was that the delete that was taking a long time
was on a different table. I tried to delete 150 rows from a table with 750
rows
