Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Albe Laurenz" <laurenz.albe@xxxxxxxxxx> 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


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux