Your DB-design depend on your application. Storing only the points plus 2-3
attributes will going into one table.
To make your db faster, there are many possibilitys:
- compound points with/without M-values
- create child-tables with the inherits-postgres-feature
- create child-tables with check-constraints, triggers and put them together
with a view
Creating child-tables will slow down extremly write performance, but on reading
the db has not to read the hole index because the check-constraints. And you
can put your tables on different tablespaces.
Ralf
-----Ursprüngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]] Im Auftrag von Clay,
Bruce
Gesendet: Mittwoch, 1. Juli 2009 19:13
An: [email protected]
Betreff: [postgis-users] large table question
We are looking into Postgres/PostGis as a possible alternative to
Oracle for one of our projects. Some of our data tables have over 800 million
data points.
Has anyone tried to put that much data into a single data table?
Does anyone have any advice on tuning Postgres/PostGis to be able to
handle large datasets?
Bruce
This message and any enclosures are intended only for the addressee.
Please
notify the sender by email if you are not the intended recipient. If
you are
not the intended recipient, you may not use, copy, disclose, or
distribute this
message or its contents or enclosures to any other person and any such
actions
may be unlawful. Ball reserves the right to monitor and review all
messages
and enclosures sent to or from this email address.
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
