Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.

From: Igor Neyman <ineyman(at)perceptron(dot)com>
To: "slapo(at)centrum(dot)sk" <slapo(at)centrum(dot)sk>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
Date: 2013-08-07 15:50:02
Message-ID: A76B25F2823E954C9E45E32FA49D70EC1BBF3A4D@mail.corp.perceptron.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

From: slapo(at)centrum(dot)sk [mailto:slapo(at)centrum(dot)sk]
Sent: Wednesday, August 07, 2013 11:34 AM
To: Igor Neyman; Pavel Stehule
Cc: pgsql-performance(at)postgresql(dot)org
Subject: RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.

I got:
"Total runtime: 9.313 ms" in pgAdmin
"Total runtime: 9.363 ms" in psql.
But timing after the query finished was 912.842 ms in psql.
 
Cheers,
 
Peter Slapansky
______________________________________________________________

That proves what Pavel suggested regarding planning time.

Regards,
Igor Neyman

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2013-08-07 15:53:14 Re: RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
Previous Message Alexis Lê-Quôc 2013-08-07 15:38:47 Better performance possible for a pathological query?