>> Although, I suspect the (dropped index + enable_seqscan) causes this, >> is the cost shown in explain output some kind of default max or >> something like that for such abnormal cases? > > When you set enable_xxx=off, it not actually disables the xxx > operation, it sets the start cost to the high value (10000000000). >
Oh, okay, thanks! -- Amit Langote -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
