On 7/22/16 3:37 AM, Robert Klemme wrote:
I am wondering what to do if the same statement has multiple execution
plans if that is possible in such a scenario. Present all the plans or
just the one with the highest impact? Show them next to each other so
the user is immediately aware that all these
Oscar Camuendo writes:
> I'm working on Postgresql 9.5.3 and executed a query which takes 5 or 7
> seconds and it should not take more than 0.30 milliseconds, the query is:
Have you ANALYZEd your tables lately? Some of these estimated row counts
seem awfully far off for no very good reason.
I'm working on Postgresql 9.5.3 and executed a query which takes 5 or 7 seconds
and it should not take more than 0.30 milliseconds, the query is:
---QUERY--
with recursive t(level,parent_id,id) as (
sel
On Fri, Jul 22, 2016 at 12:14 AM, Jim Nasby wrote:
> On 7/21/16 4:59 PM, Tom Lane wrote:
>>>
>>> > As for function plans, ISTM that could be added to the PL handlers if
>>> > we
>>> > wanted to (allow a function invocation to return an array of explain
>>> > outputs).
>>
>> Where would you put tho
fre 2016-07-22 klockan 19:08 +1200 skrev Mark Kirkwood:
> On 22/07/16 13:07, Johan Fredriksson wrote:
> > And by the way, I have also tried to upgrade to Postgresql 9.4.8 (the
> > latest version in postgresl.org's own repository) without improvment.
> >
>
> Not sure what repo you are using, but 9
On 22/07/16 13:07, Johan Fredriksson wrote:
And by the way, I have also tried to upgrade to Postgresql 9.4.8 (the latest
version in postgresl.org's own repository) without improvment.
Not sure what repo you are using, but 9.5.3 and 9.6 Beta are the
*actual* latest versions. Now I'm not sure
