<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Nachricht</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3562" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff size=2>Your
DB-design depend on your application. Storing only the points plus 2-3
attributes will going into one table.</FONT></SPAN></DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff size=2>To
make your db faster, there are many possibilitys:</FONT></SPAN></DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff size=2>
- compound points with/without M-values</FONT></SPAN></DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff size=2>
- create child-tables with the inherits-postgres-feature</FONT></SPAN></DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff size=2>
- create child-tables with check-constraints, triggers and put them together
with a view</FONT></SPAN></DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff
size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=892265206-02072009><FONT face=Arial color=#0000ff
size=2>Ralf</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=de dir=ltr align=left><FONT face=Tahoma
size=2>-----Ursprüngliche Nachricht-----<BR><B>Von:</B>
postgis-users-bounces@postgis.refractions.net
[mailto:postgis-users-bounces@postgis.refractions.net] <B>Im Auftrag von
</B>Clay, Bruce<BR><B>Gesendet:</B> Mittwoch, 1. Juli 2009 19:13<BR><B>An:</B>
postgis-users@postgis.refractions.net<BR><B>Betreff:</B> [postgis-users] large
table question<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">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.</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Has anyone tried to put that much
data into a single data table?</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Does anyone have any advice on
tuning Postgres/PostGis to be able to handle large datasets?</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Bruce</SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P></DIV><PRE>
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.</PRE></BLOCKQUOTE></BODY></HTML>