[postgis-users] CLUSTER PostGIS table

[strk at refractions.net]

On Wed, Mar 09, 2005 at 10:38:26PM +0100, strk at refractions.net wrote:
> On Wed, Mar 09, 2005 at 04:23:28PM +0100, Bernhard Reimar Hoefle wrote:
> > Hi!
> > I tried to CLUSTER a table (which holds also NULL values) with PostGIS geometry
> > on the gist index.
> > I get the following message:
> > 
> > ERROR:  cannot cluster when index access method does not handle null values
> 
> I didn't know we weren't supporting null values.
> Indeed we do... should check in pgsql manuals, but I'm pretty busy
> these days.

I took a look at this issue. The GiST access method itself does not *index*
null values:

	SELECT amname, amindexnulls from pg_am;

Use the suggested solution if you want to use clusters (add a NOT NULL clause
to your geometry column).

--strk;

> 
> > HINT:  You may be able to work around this by marking column "geom_point" NOT
> > NULL.
> > 
> > Does it make sense to CLUSTER the table on the geometry index (gist)?
> > Is there a different way to reorganise a huge table with geometry columns to get
> > better performance for spatial queries? p.s. I have 1 3D POINT geometry per
> > row.
> 
> a REINDEX ?
> 
> --strk;
> 
> > 
> > Thanks in advance,
> > Bernhard
> > 
> > 
> > 
> > 
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users