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

On Fri, Nov 30, 2012 at 9:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Albe Laurenz" <laurenz.albe@wien.gv.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.

Also possibly decompression time too.

merlin