Thanks Brent. Going to try this. I will update the progress.
Thanks,
Sairam Krishnamurthy
+1 612 859 8161
On Fri, Apr 22, 2011 at 4:08 PM, wrote:
> It is likely to be the fastest waty to initially populate the table as a
> bulk insert. There is nothing stopping you adding rows later however y
It is likely to be the fastest waty to initially populate the table as a bulk
insert. There is nothing stopping you adding rows later however you like. I
have populated tables with 250,000,000+ rows like this.
The advantage is that once the data is loaded without constraints, you can run
querie
Well ... That wont in my case because I will be adding rows to the table
later. Also it requires additional time to update the table. The table will
have millions of rows.
But is it really different from the why I am doing it right now? Will it
help in the unique constraint in any way ?
Thanks,
S
I'd try a different approach to loading your data into the table.
Try loading your lat/lon values using copy. This will be fastest (specify the
field delimiter char): eg: cat | psql -d -c "copy from
STDIN with delimiter '?';"
Then add your geometry column to the table.
select addgeometrycolu
All,
I am loading a table from a file. The file is really big and has
millions of rows. Table structure is described below:
lat : double precision (primary key)
lon: double precision (primary key)
spatialPoint: geometry (unique)
The file has lines of lat and lon: (lat,lon)
Since I am loading fr
On Fri, Apr 22, 2011 at 02:57, Paragon Corporation wrote:
>
> Mark,
> Agree with Paul -- we did say all PSC should at least feel comfortable with
> our position and be able to defend it. Though probably something we need to
> clarify in our voting rules.
>
> I've cc'd the regular users group sinc
Hello postgis list!
I have a large query, it was going good, but I wanted to add a
restriction to a path, this my WHERE clause:
WHERE
ST_Distance_Sphere(ST_GeomFromText('POINT($lat1
$lng1)'),
ST_Line_Substring(re.path, 0, 0.5)) < $rad1
another 2c (AUS) worth - but that's 2.1 US cents at the moment!
Another strictly user, but I'll go along with Brent's sentiment on this - we
are lucky that our servers are all FreeBSD - meaning that we are now running
the 9.0.3 / 1.5.2 combination straight out of ports. Upgrades (just went from
Hi,
I like give my 2ct about this question.
As readeble to this link:
http://momjian.us/main/blogs/pgblog/2011.html#April_21_2011
Between pg 8.3 and pg 8.4 there is 20% code increasing
It is the 2nd biggest increase of code compare to all other version.
Even the PG9.1 platform has less increas
