Thanks - but what do you call big?
My application is satellite data btw so the reference could be useful.
On Tue, 5 Sep 2006 01:40 pm, Oleg Bartunov wrote:
> Nick,
>
> if you need very fast spatial queries (spherical) you may use our
> Q3C module for POstgreSQL (q3c.sf.net). We use it for providing access
> to very big astronomical catalogs.
>
>
> Oleg
>
> On Tue, 5 Sep 2006, Nick Bower wrote:
> > We're considering using Postgresql for storing gridded metadata - each
> > point of our grids has a variety of metadata attached to it (including
> > lat/lon, measurements, etc) and would constitute a record in
> > Postgresql+Postgis.
> >
> > Size-wise, grids are about 4000x700 and are collected twice daily over
> > say 10 years. As mentioned, each record would have up to 50 metadata
> > attributes (columns) including geom, floats, varchars etc.
> >
> > So given 4000x700x2x365x10 > 2 billion, is this going to be a problem if
> > we will be wanting to query on datetimes, Postgis lat/lon, and
> > integer-based metadata flags?
> >
> > If however I'm forced to sub-sample the grid, what rule of thumb should I
> > be looking to be constrained by?
> >
> > Thanks for any pointers, Nick
> >
> > PS - Feel free to throw in any other ideas of grid-suitable databases :)
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> > http://archives.postgresql.org
>
> Regards,
> Oleg
> _____________________________________________________________
> Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
> Sternberg Astronomical Institute, Moscow University, Russia
> Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
> phone: +007(495)939-16-83, +007(495)939-23-83
