Re: difference in query performance due to the inclusion of a polygon geometry field

From: Ivan Marchesini <ivan(dot)marchesini(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: Mauro Rossi <mauro(dot)rossi(at)irpi(dot)cnr(dot)it>, pgsql-general(at)postgresql(dot)org
Subject: Re: difference in query performance due to the inclusion of a polygon geometry field
Date: 2012-11-30 16:30:44
Message-ID: CADxXfpCaFgLuqWGUa8+4RAZmEG61TKcxCTWwu75rxCp1q+2D_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Laurenz
Thanks but as I said I have tried using psql directly on the server. And
still there is a strong difference between the queries execution time with
and without the geometric field.
May be it is a problem of clients but I obtain the same problem with
pgadmin, psql and other servers. So I suppose it is not. :-)

Thanks
Ivan

inviato da smartphone
Il giorno 30/nov/2012 15:16, "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> ha
scritto:

> ivan marchesini wrote:
> > Concerning the problem of the same "running time" I'm really surprised
> > but I can confirm that the EXPLAIN ANALIZE time is different from the
> > query execution time.
> > probably it happen something like this:
> >
> http://bytes.com/topic/postgresql/answers/422841-explain-analyze-total-runtime-walltime
> > But we have tried to remove the fk constraints without any improvement
> >
> > Concerning the client problem, e have tried to execute the query
> > directly on the server using psql.
> > The difference is still in the order of seconds: around 10 ms VS 5000 ms
> >
> > many thanks...
> >
> > other suggestions?
>
> As I said -- could the time be spent on the client?
>
> Yours,
> Laurenz Albe
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2012-11-30 18:23:47 Re: query performance, though it was timestamps,maybe just table size?
Previous Message Merlin Moncure 2012-11-30 16:12:36 Re: difference in query performance due to the inclusion of a polygon geometry field