Re: Oddity with view

From: Tom Lane
Subject: Re: Oddity with view
Date: ,
Msg-id: 11916.1226341898@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: Oddity with view  (Jim 'Decibel!' Nasby)
List: pgsql-performance

Tree view

Oddity with view  (Jim 'Decibel!' Nasby, )
 Re: Oddity with view  (Tom Lane, )
  Re: Oddity with view  (Jim 'Decibel!' Nasby, )
   Re: Oddity with view  (Richard Huxton, )
    Re: Oddity with view (now with test case)  (Jim 'Decibel!' Nasby, )
     Re: Oddity with view (now with test case)  (Tom Lane, )
      Re: Oddity with view (now with test case)  (Jim 'Decibel!' Nasby, )
       Re: Oddity with view (now with test case)  (Tom Lane, )
        Re: Oddity with view (now with test case)  (Jim 'Decibel!' Nasby, )
         Re: Oddity with view (now with test case)  (Tom Lane, )
          Re: Oddity with view (now with test case)  (Jim 'Decibel!' Nasby, )
           Re: Oddity with view (now with test case)  (Tom Lane, )
   Re: Oddity with view  (Tom Lane, )

"Jim 'Decibel!' Nasby" <> writes:
> How on earth did the seqscan suddenly take 4x longer? And why is the
> subquery scan then doubling the amount of time again?

Maybe the disk access is less sequential because of the need to fetch
the other table too?

            regards, tom lane


pgsql-performance by date:

From: Jim 'Decibel!' Nasby
Date:
Subject: Re: Oddity with view (now with test case)
From: Tom Lane
Date:
Subject: Re: Oddity with view (now with test case)