Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
От | Igor Neyman |
---|---|
Тема | Re: Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it. |
Дата | |
Msg-id | A76B25F2823E954C9E45E32FA49D70EC1BBF393A@mail.corp.perceptron.com обсуждение исходный текст |
Ответ на | RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it. (<slapo@centrum.sk>) |
Ответы |
RE: [PERFORM] Re: [PERFORM] Sub-optimal plan for a paginated query on a view with another view inside of it.
|
Список | pgsql-performance |
From: slapo@centrum.sk [mailto:slapo@centrum.sk] Sent: Wednesday, August 07, 2013 10:43 AM To: Igor Neyman; Pavel Stehule Cc: pgsql-performance@postgresql.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
В списке pgsql-performance по дате отправления: