Search Postgresql Archives

Are there any major benefits to using point and not real data type

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

 



I am using postgres 9.4 and am new to this but I have 2 columns right now
latitudes & longitudes. I have them saved as a real column so they take up 4
bits each 8 altogether. I see that point is used for latitudes and
longitudes but it is a whopping 16 bits are there any benefits (Performance)
of using point over real datatype for coordinates? I plan on using indexes
on the column and do receive a lot of inserts .



--
View this message in context: http://postgresql.nabble.com/Are-there-any-major-benefits-to-using-point-and-not-real-data-type-tp5870626.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


-- 
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