Re: inserting 4800 records at a time

Good Evening Tom-

probably the one good reason to use Postgres is the ability to install PostGIS
http://postgis.refractions.net/docs/ch04.html#id2673328 supports these simple curve geometries
CompoundCurve
CurvePolygon
MultiCurve

Does this help ?
Martin--
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: "Tom Brown" <brown(at)esteem(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Wednesday, March 28, 2007 7:30 PM
Subject: [GENERAL] inserting 4800 records at a time

> Hi,
>
> We use an application that generates 4800 points for the graph of a waveform.
> We capture this data and display it to the user. Now we want to save all this
> information to a database. I have tried to create a record for each point,
> but insertion/retrieval is slow. I thought that maybe I could save one record
> per graph and save all the points as a large string, but there would be 148k
> characters in the string. Then I'm still not sure what the performance would
> be like. Would the use of BLOBs a better way to go here? Any ideas on what
> the best approach would be for us?
>
> Thanks,
> Tom
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>