mirror of
https://git.osgeo.org/gitea/postgis/postgis
synced 2024-10-23 16:42:35 +00:00
Updates in anticipation of 0.8.2 release
git-svn-id: http://svn.osgeo.org/postgis/trunk@558 b70326c6-7e19-0410-871a-916f4a2858ee
This commit is contained in:
parent
a66c0642e5
commit
dce969ac46
18
CHANGES
18
CHANGES
|
@ -1,3 +1,21 @@
|
|||
PostGIS 0.8.2
|
||||
2004/05/27
|
||||
|
||||
- New Things
|
||||
- PgSQL 7.5 Support
|
||||
- Integrated PgSQL 7.5 statistics rathering
|
||||
- Improved schema support
|
||||
- Optional experimental lightweight geometries (LWGEOM)
|
||||
- Faster performance
|
||||
- Lower disk usage
|
||||
- Multi() function to create MULTI* geometries
|
||||
- line_interpolate_point() function for linear referencing
|
||||
- Bug Fixes
|
||||
- Minor memory leaks gone
|
||||
- Solaris support cleaner
|
||||
- shp2pgsql/pgsql2shp more corner cases fixed
|
||||
|
||||
|
||||
PostGIS 0.8.1
|
||||
2004/01/12
|
||||
|
||||
|
|
2
CREDITS
2
CREDITS
|
@ -33,4 +33,6 @@ Version 0.7 of PostGIS includes patches from:
|
|||
Version 0.8 of PostGIS includes patches from:
|
||||
Carl Anderson on schemas
|
||||
STRK on numerous bug fixes and enhancements
|
||||
Ralph Mason on WKT parsing for LWGEOM
|
||||
Mark Cave-Ayland with help on PgSQL 7.5 statistics
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
PostGIS - Geographic Information Systems Extensions to PostgreSQL
|
||||
~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
VERSION: 0.8.1 (2004/01/12)
|
||||
VERSION: 0.8.2 (2004/05/27)
|
||||
|
||||
MORE INFORMATION: http://postgis.refractions.net
|
||||
|
||||
|
@ -172,13 +172,3 @@ Always run the "VACUUM ANALYZE <tablename>" on your tables after
|
|||
creating an index. This gathers statistics which the query planner
|
||||
uses to optimize index usage.
|
||||
|
||||
Note that PostgreSQL may occasionally not use the GiST indexes when
|
||||
performing searches. If you find your system is not using the
|
||||
indexes automatically (use 'EXPLAIN' to see the query plan)
|
||||
you can force index use with the command:
|
||||
|
||||
SET ENABLE_SEQSCAN = OFF
|
||||
|
||||
Try doing an EXPLAIN on your query before and after the 'enable_seqscan'
|
||||
command to see the different query plans.
|
||||
|
||||
|
|
Loading…
Reference in a new issue