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 14:48:14 |
Message-ID: | A76B25F2823E954C9E45E32FA49D70EC1BBF393A@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 10:43 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.
You're right, it does... but it's quite odd, because I re-ran the explain-analyze statement and got the same results.
Still, the query now runs for about a second as mentioned before, so it's almost like something's missing from the explain, but I'm certain I copied it all.
I did this via pgadmin, but that shouldn't matter, should it?
Thank you,
Peter Slapansky
______________________________________________________________
_________________________________________________________
At very end of explain analyze output there should be a line:
Total runtime: ....
What do you get there?
Regards,
Igor Neyman
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-08-07 14:48:22 | Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it. |
Previous Message | slapo | 2013-08-07 14:42:50 | RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it. |