On Thu, Jun 26, 2003 at 07:32:02 -0700,
Ryan Mack <[EMAIL PROTECTED]> wrote:
> The query planner does an abysmal job with some of the most important
> views in my DB. The execuation time with seq_scan disabled is 25ms versus
> 110ms when seq_scan is enabled. Instead of modifying all my code to
The query planner does an abysmal job with some of the most important
views in my DB. The execuation time with seq_scan disabled is 25ms versus
110ms when seq_scan is enabled. Instead of modifying all my code to
temporarily disable seq_scan around all places this query is made (or
making a proced
