Re: index scan of whole table, can't see why

This is a multi-part message in MIME format.

--bound1106197232
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Let's see if I have been paying enough attention to the SQL gurus. The planner is making a different estimate of how
manydeprecated<>'' versus how many broken <> ''. I would try SET STATISTICS to a larger number on the ports table, and
re-analyze.

--bound1106197232--