Dear Andrea,
thank you for this deep insight into why Postgres/PostGIS with GeoServer
rocks! You were totally right!
I just made an exact clone of the lightning table in PostGIS and there
is no observable difference in performance whether I'm looking at whole
Europe (just a couple hundred
Hi Andrea,
I wasn't trying to downplay your penchant to push PostGres, it's something
I understand and agree with. Your explanation of the differences was very
informative - I've seen posts mentioning them in passing before, but this was a
little more in depth, thanks for sharing.
Cheers,
On Wed, Jun 22, 2016 at 2:15 PM, Jonathan Moules <
jonathan-li...@lightpear.com> wrote:
> While Andrea has an (understandable) leaning towards PostGres, I'd be
> surprised if you can't optimise Oracle to get the desired result too if
> you're fixed with that (but if you're not - PostGres would
Hi Peter,
To build on the other answers you've received - you need to create indexes that
the database will use. This applies to all relational databases - Oracle/SQL
Server/PostGres/Sqlite, etc.
When you send a query to a database there's a query planner which takes your
query and tries to
ver-users@lists.sourceforge.net>
Emne: Re: [Geoserver-users] How to serve large spatio-temporal dataset with
GeoServer?
Hi Andrea,
what do you mean with "deciding which one to use"? AFAIK it has to use both,
(almost) all the time.
This is the query found in GeoServer logs (LOCATION is the
On Wed, Jun 22, 2016 at 10:02 AM, Peter Kovac wrote:
> Hi Andrea,
>
> what do you mean with "deciding which one to use"? AFAIK it has to use
> both, (almost) all the time.
>
According to what Bruce Momjan told me a few years ago, not always. He was
going over some
Hi Peter,
from my experience Oracle is probably the cause, given a spatial and a
regular index
it has sometimes issues deciding which one to use and ends up using the
wrong one.
You should try PostGis, with proper indexes and statistics setup, with
"only" 3 million records
it should respond fast.
Hi Peter,
Are you always querying for a short time period? If so, you might get
the most mileage out of a SQL database (Oracle/Postgres) by creating an
index on time and providing any vendor specific query hints to leverage
that index. From a GeoTools/GeoServer perspective, WMS/WFS queries