Re: Indexing large table of coordinates with GiST

From: Rémi Cura <remi(dot)cura(at)gmail(dot)com>
To: Andy Colson <andy(at)squeakycode(dot)net>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Indexing large table of coordinates with GiST
Date: 2015-01-15 16:43:52
Message-ID: CAJvUf_uO5iG8PVdvLkaHxBVDXzYmZwMAdWdvsknVMQ=mSBG+KQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hey,
You may want to post this on postGIS list.

I take that so many rows mean either raster or point cloud.
If it is point cloud simply consider using pg_pointcloud.
A 6 billion point cloud is about 600 k lines for one of my data set.

If it is raster, you may consider using postgis raster type.
If you really want to keep that much geometry,
you may want to partition your data on a regular grid.
Cheers,
Rémi-C

2015-01-15 15:45 GMT+01:00 Andy Colson <andy(at)squeakycode(dot)net>:

> On 1/15/2015 6:44 AM, Daniel Begin wrote:
>
>> Hi, I'm trying to create an index on coordinates (geography type) over a
>> large table (4.5 billion records) using GiST...
>>
>> CREATE INDEX nodes_geom_idx ON nodes USING gist (geom);
>>
>> The command ran for 5 days until my computer stops because a power outage!
>> Before restarting the index creation, I am asking the community if there
>> are
>> ways to shorten the time it took the first time :-)
>>
>> Any idea?
>>
>> Daniel
>>
>>
>>
>>
> Set maintenance_work_mem as large as you can.
>
> -Andy
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2015-01-15 17:04:55 Re: can you have any idea about toast missing chunk issu resolution
Previous Message Rob Sargent 2015-01-15 16:41:04 Re: Indexing large table of coordinates with GiST