[postgis-tickets] [PostGIS] #2798: raster2pgsql spins CPU on statement timeout
PostGIS
trac at osgeo.org
Mon Jun 30 10:56:59 PDT 2014
#2798: raster2pgsql spins CPU on statement timeout
----------------------+-----------------------------------------------------
Reporter: strk | Owner: dustymugs
Type: defect | Status: new
Priority: critical | Milestone:
Component: raster | Version: trunk
Keywords: |
----------------------+-----------------------------------------------------
After waiting for an hour that a raster import completed, with CPU coolers
screaming as hell, I finally went looking in pg_stat_activity and found
that the transaction was aborted due to a timeout:
{{{
state | idle in transaction (aborted)
query | COPY "timeseq_change00_12" ("rast") FROM stdin;
}}}
This occurrence evidently did not stop raster2pgsql which took away my CPU
and tried to kill it.
This is with current PostGIS trunk and GDAL 1.11.0
The test dataset is "Indonesia time-sequential primary forest extent and
loss" http://glad.geog.umd.edu/indonesia/data2014/index.html
The import command:
{{{
raster2pgsql -C -I -s 4326 -Y -t 256x256 \
timeseq_change00_12.tif timeseq_change00_12
}}}
Some top(1) extracts:
{{{
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
13229 strk 20 0 222m 47m 2068 R 99.2 1.2 58:00.08 raster2pgsql
13230 strk 20 0 29160 1192 924 S 0.7 0.0 0:22.77 psql
13231 strk 20 0 181m 10m 6340 S 0.7 0.3 0:32.82 postgres
}}}
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2798>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list