Changes between Version 27 and Version 28 of DevWikiGardenTest

Timestamp:

12/03/10 05:13:26 (14 years ago)

Author:

robe

Comment:

--

DevWikiGardenTest

@@ -15 +15 @@
    columns are: logid-  an autonumber, log_label - a short description, spatial_class - (will contain geometry or geography), func - name of function being tested, g1 - type of geometry of first geometry, g2 - type of geometry of second or null if a single geometry function, log_start - start time (timestamp), log_end - end time (timestamp), log_sql - the SQL statement that was run.
 
-If the test crashes before completion, the record with the largest logid will tell you the query that crashed the server..
+If the test crashes before completion, the record with the largest logid will tell you the query that crashed the server.
 
  * postgis_garden_log_output -- this outputs the query results for queries that return something in xml format.  It  uses the built-in query_to_xml function that has existed since PostgreSQL 8.3 to do that.
@@ -22 +22 @@
    * log_output - an xml field that contains the query_to_xml output of the query.
 
-The really nice benefit about logging the query and the output to a table, is that it's easier to inspect and you can also rerun a subset of the queries for closer inspection by just writing an sql statement something like below -- which will test all tests for the ST_Distance function that involve points and linestrings
+* There is also a companion for raster testing: raster_gardentest.sql.xsl .The raster one doesn't
+currently create logging labels but will soon.
+
+-- to run:
+-- create the tests
+There is an unfortunate dependency on postgis_agg_mm.xml which is really not needed 
+just create a dummy blank file called postgis_agg_mm.xml in the trunk/doc to get around this
+Then:
+{{{
+xsltproc -o geo_torturetest.sql trunk/doc/xsl/postgis_gardentest.sql.xsl trunk/doc/postgis.xml
+xsltproc -o rast_torturetest.sql trunk/doc/xsl/raster_gardentest.sql.xsl trunk/doc/postgis.xml
+}}}
+
+-- run them
+{{{
+psql -p 5432 -U postgres -d postgres -c "DROP DATABASE testpostgis;"
+psql -p 5432 -U postgres -d postgres -c "CREATE DATABASE testpostgis;" 
+psql -p 5432 -U postgres -d testpostgis -c "CREATE LANGUAGE plpgsql;" 
+psql -p 5432 -U postgres -d testpostgis -f postgis.sql 
+psql -p 5432 -U postgres -d testpostgis -f spatial_ref_sys.sql
+psql -p 5432 -U postgres -d testpostgis -f rtpostgis.sql 
+psql -p 5432 -U postgres -d testpostgis -f geo_torturetest.sql > geo_torturetest_results.txt 
+psql -p 5432 -U postgres -d testpostgis -f rast_torturetest.sql > rast_torturetest_results.txt   
+
+}}}
+
+One nice benefit about logging the query and the output to a table, is that it's easier to inspect (and you can conceivably do a join between too logging tables to compare results from test to test) and you can also rerun a subset of the queries for closer inspection by just writing an sql statement something like below -- which will test all tests for the ST_Distance function that involve points and linestrings
 
 {{{
@@ -33 +59 @@
 }}}
 
+You can even do even more cool things like use [http://developer.postgresql.org/pgdocs/postgres/pgbench.html pgbench] to simulate users with a transaction script that 
+looks something like the below script that will run 10 function queries on functions that
+start with ST_ that have succeeded in the past.
 
-There is an unfortunate dependency on postgis_agg_mm.xml which is really not needed 
-just create a dummy blank file called postgis_agg_mm.xml in the trunk/doc to get around this
-Then:
-{{{
-xsltproc -o torturetest.sql trunk/doc/xsl/postgis_gardentest.sql.xsl trunk/doc/postgis.xml
+{{{BEGIN;
+SELECT query_to_xml(log_sql) FROM postgis_garden_log  WHERE func LIKE 'ST_%'
+and log_end IS NOT NULL ORDER BY random() LIMIT 10;
+  END;
 }}}
+
 
 == Version PostGIS 1.5+ ==