Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3

From: Tom Lane
Subject: Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3
Date: ,
Msg-id: 2335.1173798373@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>)
Responses: Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>)
List: pgsql-performance

Tree view

Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )
 Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (Michael Fuhr, )
  Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )
   Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (Richard Huxton, )
    Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )
     Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  ("Dave Dutcher", )
      Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )
       Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  ("Dave Dutcher", )
     Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (Richard Huxton, )
   Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (Alvaro Herrera, )
    Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )
     Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (Alvaro Herrera, )
      Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )
       Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (Tom Lane, )
        Re: Execution plan changed after upgrade from 7.3.9 to 8.2.3  (<>, )

<> writes:
> I was able to improve response time by seting enable_seqscan to off

enable_nestloop = off would probably be a saner choice, at least for
this particular query.

            regards, tom lane


pgsql-performance by date:

From: Cosimo Streppone
Date:
Subject: Re: PostgreSQL in virtual machine
From: "Anton Melser"
Date:
Subject: Re: PostgreSQL 8.2.3 VACUUM Timings/Performance