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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: ivan(dot)marchesini(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org, "Mauro Rossi" <mauro(dot)rossi(at)irpi(dot)cnr(dot)it>
Subject: Re: difference in query performance due to the inclusion of a polygon geometry field
Date: 2012-11-30 15:51:50
Message-ID: 13311.1354290710@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:
> As I said -- could the time be spent on the client?

It is probably some combination of

(1) time to fetch the wide geometry values from the table's TOAST table
(2) time to convert the geometry values to text form
(3) time to transmit the larger volume of data to the client
(4) client-side processing time

None of these costs are expended in an EXPLAIN ANALYZE, which is
why the time reported for that doesn't change materially.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2012-11-30 16:12:36 Re: difference in query performance due to the inclusion of a polygon geometry field
Previous Message Devrim GÜNDÜZ 2012-11-30 15:40:40 Re: Mailing list Question