From: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
To: pgsql-performance@postgresql.org
Subject: Re: Insert performance
Date: Tue, 19 Aug 2003 12:03:26 +0530
Message-ID: <3F42120E.28901.E71BBDF@localhost> (raw)
In-Reply-To: <1061245017.2620.14.camel@fuji.krosing.net>
References: <3F4145EB.20645.B5452D9@localhost>
On 19 Aug 2003 at 1:16, Hannu Krosing wrote:
> Shridhar Daithankar kirjutas E, 18.08.2003 kell 19:02:
> > I was loading a geographic data couple of months back.. It was 3GB data when
> > loaded in postgresql.
>
> With or without indexes ?
Without index. Index was another 3 GB with 50% utilisation. It was 81M rows
with 3 floats each..
>
> > I tried loading data first and creating index later. It ran out of available
> > 9GB space. So I created index on an empty table and started loading it. It was
> > slow but at least finished after 3 hours... Co-incidentally oracle had same
> > problems as well. So creating index beforehand remains only option at times, it
> > seems. Tom remarked that it shouldn't have made difference but apparently it
> > does..
>
> Tom just fixed some memory leaks on array indexing the other day. Could
> there be something like that on geographic types ?
Dunno.. This was 7.3.2 or earlier.. Later the project abandoned all types of
databases and went to in memory structures since flat data was of the order of
200MB. Now they aer returning to databases as flat data is approaching excess
of 3 GB..
God knows what will they do next. It's an ideal example what schedule pressure
can do to architecture design of a software..
Bye
Shridhar
--
Air Force Inertia Axiom: Consistency is always easier to defend than correctness.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: shridhar_daithankar@persistent.co.in
Subject: Re: Insert performance
In-Reply-To: <3F42120E.28901.E71BBDF@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox