<div dir="ltr">Going back a few messages, it looks like you're specifying these out-db rasters with relative paths. Use absolute paths.<div><br></div><div>Instead of:</div><div><br></div><div><font face="monospace, monospace"><span style="font-size:13px">raster2pgsql -I -C -e -Y -F -d -R -s 2926 ./slope/slope_ps.tif gis.slope | psql osm_test</span><br></font></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">Use:</span></div><div><span style="font-size:13px"><br></span></div><div><div><span style="font-size:13px"><font face="monospace, monospace">raster2pgsql -I -C -e -Y -F -d -R -s 2926 /ABSOLUTE/PATH/TO/slope/slope_ps.tif gis.slope | psql osm_test</font></span><br></div></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">PostgreSQL cannot access paths that were relative to the current working directory when calling raster2pgsql.</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">Also, specify a tile size.</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">-bborie</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 25, 2015 at 12:51 PM, Phil Hurvitz <span dir="ltr"><<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you, Bborie. This seems to be a partial solution (at least now PostGIS isn't complaining about the out-db raster). But now I get a different problem, which is that attempting to access the out-db raster makes the connection choke:<br>
<br>
select st_summarystats(rast) from slope;<br>
The connection to the server was lost. Attempting reset: Failed.<br>
!><span class=""><br>
<br>
-P.<br>
<br>
******************************<u></u>******************************<u></u>**<br>
Philip M. Hurvitz, PhD | Research Assistant Professor | UW-CBE<br>
Urban Form Lab | 1107 NE 45th Street, Suite 535 | Box 354802<br>
University of Washington, Seattle, Washington 98195-4802, USA<br>
<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.edu</a> | <a href="http://gis.washington.edu/phurvitz" target="_blank">http://gis.washington.edu/<u></u>phurvitz</a><br>
"What is essential is invisible to the eye." -de Saint-Exupéry<br>
******************************<u></u>******************************<u></u>**<br>
<br></span><span class="">
On 2/25/2015 12:41, Bborie Park wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Ah. I use a script similar to this.<br>
<br>
In the following block...<br>
<br>
start)<br>
...<br>
su - $PGUSER -c "$DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1<br>
...<br>
<br>
You'll want to modify the su line to be like:<br>
<br>
su - $PGUSER -c "POSTGIS_ENABLE_OUTDB_RASTERS=<u></u>1<br></span>
POSTGIS_GDAL_ENABLED_DRIVERS=_<u></u>_ENABLE_ALL $DAEMON -D '$PGDATA' &"<span class=""><br>
>>$PGLOG 2>&1<br>
<br>
See if that works...<br>
<br>
-bborie<br>
<br>
<br>
On Wed, Feb 25, 2015 at 12:29 PM, Phil Hurvitz <<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a><br></span><div><div class="h5">
<mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>>> wrote:<br>
<br>
Certainly!<br>
<br>
! /bin/sh<br>
<br>
# chkconfig: 2345 98 02<br>
# description: PostgreSQL RDBMS<br>
<br>
# This is an example of a start/stop script for SysV-style init, such<br>
# as is used on Linux systems. You should edit some of the variables<br>
# and maybe the 'echo' commands.<br>
#<br>
# Place this file at /etc/init.d/postgresql (or<br>
# /etc/rc.d/init.d/postgresql) and make symlinks to<br>
# /etc/rc.d/rc0.d/K02postgresql<br>
# /etc/rc.d/rc1.d/K02postgresql<br>
# /etc/rc.d/rc2.d/K02postgresql<br>
# /etc/rc.d/rc3.d/S98postgresql<br>
# /etc/rc.d/rc4.d/S98postgresql<br>
# /etc/rc.d/rc5.d/S98postgresql<br>
# Or, if you have chkconfig, simply:<br>
# chkconfig --add postgresql<br>
#<br>
# Proper init scripts on Linux systems normally require setting lock<br>
# and pid files under /var/run as well as reacting to network<br>
# settings, so you should treat this with care.<br>
<br>
# Original author: Ryan Kirkpatrick <<a href="mailto:pgsql@rkirkpat.net" target="_blank">pgsql@rkirkpat.net</a><br></div></div>
<mailto:<a href="mailto:pgsql@rkirkpat.net" target="_blank">pgsql@rkirkpat.net</a>>><span class=""><br>
<br>
# contrib/start-scripts/linux<br>
<br>
## EDIT FROM HERE<br>
<br>
# Installation prefix<br>
prefix=/usr/local/pgsql<br>
<br>
# Data directory<br>
PGDATA="/usr/local/pgsql/data"<br></span>
POSTGIS_GDAL_ENABLED_DRIVERS=_<u></u>_ENABLE_ALL<span class=""><br>
<br>
# Who to run the postmaster as, usually "postgres". (NOT "root")<br>
PGUSER=postgres<br>
<br>
# Where to keep a log file<br>
PGLOG="$PGDATA/serverlog"<br>
<br>
# It's often a good idea to protect the postmaster from being killed<br>
by the<br>
# OOM killer (which will tend to preferentially kill the postmaster<br>
because<br>
# of the way it accounts for shared memory). Setting the<br>
OOM_SCORE_ADJ value<br>
# to -1000 will disable OOM kill altogether. If you enable this,<br>
you probably<br>
# want to compile PostgreSQL with "-DLINUX_OOM_SCORE_ADJ=0", so that<br>
# individual backends can still be killed by the OOM killer.<br>
#OOM_SCORE_ADJ=-1000<br>
# Older Linux kernels may not have /proc/self/oom_score_adj, but instead<br>
# /proc/self/oom_adj, which works similarly except the disable value<br>
is -17.<br>
# For such a system, enable this and compile with "-DLINUX_OOM_ADJ=0".<br>
#OOM_ADJ=-17<br>
<br>
POSTGIS_ENABLE_OUTDB_RASTERS=1<br></span>
POSTGIS_GDAL_ENABLED_DRIVERS=_<u></u>_ENABLE_ALL<span class=""><br>
<br>
## STOP EDITING HERE<br>
<br>
# The path that is to be used for the script<br></span>
PATH=/usr/local/sbin:/usr/__<u></u>local/bin:/sbin:/bin:/usr/__<u></u>sbin:/usr/bin<span class=""><br>
<br>
# What to use to start up the postmaster. (If you want the script<br>
to wait<br>
# until the server has started, you could use "pg_ctl start -w" here.<br>
# But without -w, pg_ctl adds no value.)<br></span>
DAEMON="$prefix/bin/__<u></u>postmaster"<div><div class="h5"><br>
<br>
# What to use to shut down the postmaster<br>
PGCTL="$prefix/bin/pg_ctl"<br>
<br>
set -e<br>
<br>
# Only start if we can find the postmaster.<br>
test -x $DAEMON ||<br>
{<br>
echo "$DAEMON not found"<br>
if [ "$1" = "stop" ]<br>
then exit 0<br>
else exit 5<br>
fi<br>
}<br>
<br>
<br>
# Parse command line parameters.<br>
case $1 in<br>
start)<br>
echo -n "Starting PostgreSQL: "<br>
test x"$OOM_SCORE_ADJ" != x && echo "$OOM_SCORE_ADJ" ><br>
/proc/self/oom_score_adj<br>
test x"$OOM_ADJ" != x && echo "$OOM_ADJ" > /proc/self/oom_adj<br>
su - $PGUSER -c "$DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1<br>
echo "ok"<br>
;;<br>
stop)<br>
echo -n "Stopping PostgreSQL: "<br>
su - $PGUSER -c "$PGCTL stop -D '$PGDATA' -s -m fast"<br>
echo "ok"<br>
;;<br>
restart)<br>
echo -n "Restarting PostgreSQL: "<br>
su - $PGUSER -c "$PGCTL stop -D '$PGDATA' -s -m fast -w"<br>
test x"$OOM_SCORE_ADJ" != x && echo "$OOM_SCORE_ADJ" ><br>
/proc/self/oom_score_adj<br>
test x"$OOM_ADJ" != x && echo "$OOM_ADJ" > /proc/self/oom_adj<br>
su - $PGUSER -c "$DAEMON -D '$PGDATA' &" >>$PGLOG 2>&1<br>
echo "ok"<br>
;;<br>
reload)<br>
echo -n "Reload PostgreSQL: "<br>
su - $PGUSER -c "$PGCTL reload -D '$PGDATA' -s"<br>
echo "ok"<br>
;;<br>
status)<br>
su - $PGUSER -c "$PGCTL status -D '$PGDATA'"<br>
;;<br>
*)<br>
# Print help<br></div></div>
echo "Usage: $0 {start|stop|restart|reload|__<u></u>status}" 1>&2<span class=""><br>
exit 1<br>
;;<br>
esac<br>
<br>
exit 0<br>
<br>
-P.<br>
<br></span><span class="">
******************************<u></u>__****************************<u></u>**__**<br>
Philip M. Hurvitz, PhD | Research Assistant Professor | UW-CBE<br>
Urban Form Lab | 1107 NE 45th Street, Suite 535 | Box 354802<br>
University of Washington, Seattle, Washington 98195-4802, USA<br>
<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.edu</a> <mailto:<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.<u></u>edu</a>> |<br>
<a href="http://gis.washington.edu/__phurvitz" target="_blank">http://gis.washington.edu/__<u></u>phurvitz</a><br>
<<a href="http://gis.washington.edu/phurvitz" target="_blank">http://gis.washington.edu/<u></u>phurvitz</a>><br>
"What is essential is invisible to the eye." -de Saint-Exupéry<br>
******************************<u></u>__****************************<u></u>**__**<br>
<br></span><span class="">
On 2/25/2015 12:25, Bborie Park wrote:<br>
<br>
Can you post the shell script?<br>
<br>
<br>
<br>
On Wed, Feb 25, 2015 at 11:50 AM, Phil Hurvitz <<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a><br>
<mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>><br></span><span class="">
<mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a> <mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>>>> wrote:<br>
<br></span><span class="">
Thanks Bborie, I am starting with a shell script, and have<br>
added the<br>
env vars to that script, but am still unable to access the<br>
out-db<br>
rasters.<br>
<br>
-P.<br>
<br>
<br></span><span class="">
******************************<u></u>____**************************<u></u>**__**__**<br>
Philip M. Hurvitz, PhD | Research Assistant Professor | UW-CBE<br>
Urban Form Lab | 1107 NE 45th Street, Suite 535 | Box 354802<br>
University of Washington, Seattle, Washington 98195-4802, USA<br>
<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.edu</a> <mailto:<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.<u></u>edu</a>><br>
<mailto:<a href="mailto:phurvitz@u.washington." target="_blank">phurvitz@u.washington.</a><u></u>__edu<br>
<mailto:<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.<u></u>edu</a>>> |<br>
<a href="http://gis.washington.edu/____phurvitz" target="_blank">http://gis.washington.edu/____<u></u>phurvitz</a><br>
<<a href="http://gis.washington.edu/__phurvitz" target="_blank">http://gis.washington.edu/__<u></u>phurvitz</a>><br>
<<a href="http://gis.washington.edu/__phurvitz" target="_blank">http://gis.washington.edu/__<u></u>phurvitz</a><br>
<<a href="http://gis.washington.edu/phurvitz" target="_blank">http://gis.washington.edu/<u></u>phurvitz</a>>><br>
"What is essential is invisible to the eye." -de Saint-Exupéry<br>
<br>
******************************<u></u>____**************************<u></u>**__**__**<br>
<br></span><span class="">
On 2/25/2015 11:45, Bborie Park wrote:<br>
<br>
The env variables need to be within the environment of<br>
the postgres<br>
process. How are you starting postgres?<br>
<br>
Shell script? Then you should be able to add the<br>
variables to<br>
that script.<br>
<br>
Direct invocation of posrgres on the command line? You<br>
need to<br>
have the<br>
variables before the command<br>
<br>
VAR=1 postgres ...<br>
<br>
-bborie<br>
<br>
On Feb 25, 2015 11:40 AM, "Phil Hurvitz"<br>
<<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a> <mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>><br>
<mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a> <mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>>><br>
<mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a> <mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>><br>
<mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a> <mailto:<a href="mailto:phurvitz@uw.edu" target="_blank">phurvitz@uw.edu</a>>>>> wrote:<br>
<br>
Thanks Bborie, I built from the tarball rather<br>
than using<br>
an rpm;<br>
does that still mean I should be adding the<br>
environment<br>
variables to<br>
<br></span>
/etc/sysconfig/pgsql/______<u></u>postgresql<span class=""><br>
<br>
So for overkill I added the env vars to that file<br>
as well<br>
as to the<br>
init script, restarted PostgreSQL, and it seems I<br>
still cannot<br>
access the out-db raster.<br>
<br>
I added a slope raster using:<br>
<br>
raster2pgsql -I -C -e -Y -F -d -R -s 2926<br>
./slope/slope_ps.tif<br>
gis.slope | psql osm_test<br>
<br>
I can get metadata (sorry for the ugly text wrapping):<br>
<br>
select rid, (<a href="http://foo.md" target="_blank">foo.md</a> <<a href="http://foo.md" target="_blank">http://foo.md</a>><br>
<<a href="http://foo.md" target="_blank">http://foo.md</a>> <<a href="http://foo.md" target="_blank">http://foo.md</a>>).* from<br>
(select rid,<br>
st_Metadata(rast) as md from slope) as foo;<br>
rid | upperleftx | upperlefty |<br>
width | height |<br>
scalex | scaley | skewx | skewy |<br>
srid |<br>
numbands<br>
<br>
<br></span>
-----+------------------+-----<u></u>______-------------+-------+--<u></u>--__--__--__+-----------------<u></u>-+--__----__----__---------+--<u></u>-----+__------__-+----__--+---<u></u>-------<span class=""><br>
1 | 835161.301005914 | 758483.868026069 |<br>
31935 | 34649 |<br>
32.8083333333333 | -32.8083333333333 | 0 |<br>
0 | 2926<br>
| 1<br>
<br>
But cannot access values:<br>
<br>
select st_summarystats(rast) from slope;<br>
ERROR: rt_raster_load_offline_data: Access to offline<br>
bands disabled<br>
CONTEXT: SQL function "st_summarystats" statement 1<br>
<br>
select st_value(rast, 1, 1, 1) from slope;<br>
ERROR: rt_raster_load_offline_data: Access to offline<br>
bands disabled<br>
<br>
-P.<br>
<br>
<br>
<br></span>
******************************<u></u>______************************<u></u>**__**__**__**<span class=""><br>
Philip M. Hurvitz, PhD | Research Assistant<br>
Professor | UW-CBE<br>
Urban Form Lab | 1107 NE 45th Street, Suite 535<br>
| Box 354802<br>
University of Washington, Seattle, Washington<br>
98195-4802, USA<br>
<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.edu</a> <mailto:<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.<u></u>edu</a>><br>
<mailto:<a href="mailto:phurvitz@u.washington." target="_blank">phurvitz@u.washington.</a><u></u>__edu<br>
<mailto:<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.<u></u>edu</a>>><br></span>
<mailto:<a href="mailto:phurvitz@u.washington" target="_blank">phurvitz@u.washington</a>.<br>
<mailto:<a href="mailto:phurvitz@u.washington" target="_blank">phurvitz@u.washington</a>.<u></u>>____edu<br>
<mailto:<a href="mailto:phurvitz@u.washington." target="_blank">phurvitz@u.washington.</a><u></u>__edu<br>
<mailto:<a href="mailto:phurvitz@u.washington.edu" target="_blank">phurvitz@u.washington.<u></u>edu</a>>>> |<br>
<a href="http://gis.washington.edu/______phurvitz" target="_blank">http://gis.washington.edu/____<u></u>__phurvitz</a><br>
<<a href="http://gis.washington.edu/____phurvitz" target="_blank">http://gis.washington.edu/___<u></u>_phurvitz</a>><span class=""><br>
<<a href="http://gis.washington.edu/____phurvitz" target="_blank">http://gis.washington.edu/___<u></u>_phurvitz</a><br>
<<a href="http://gis.washington.edu/__phurvitz" target="_blank">http://gis.washington.edu/__<u></u>phurvitz</a>>><br>
<<a href="http://gis.washington.edu/____phurvitz" target="_blank">http://gis.washington.edu/___<u></u>_phurvitz</a><br>
<<a href="http://gis.washington.edu/__phurvitz" target="_blank">http://gis.washington.edu/__<u></u>phurvitz</a>><br>
<<a href="http://gis.washington.edu/__phurvitz" target="_blank">http://gis.washington.edu/__<u></u>phurvitz</a><br>
<<a href="http://gis.washington.edu/phurvitz" target="_blank">http://gis.washington.edu/<u></u>phurvitz</a>>>><br>
"What is essential is invisible to the eye." -de<br>
Saint-Exupéry<br>
<br>
<br></span>
******************************<u></u>______************************<u></u>**__**__**__**<span class=""><br>
<br>
<br>
Bborie Park <a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a><br>
<mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a>><br>
<mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a><br></span>
<mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a>>> <mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a><br>
<mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a>><br>
<mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a> <mailto:<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a>>>><span class=""><br>
Wed Feb 25 10:46:59 PST 2015<br>
<br>
><br>
<br>
Philip,<br>
<br>
POSTGIS_ENABLE_OUTDB_RASTERS=1 is an environment<br>
variable not to<br>
be in<br>
postgresql.conf.<br>
<br>
The same is true for<br></span>
POSTGIS_GDAL_ENABLED_DRIVERS=_<u></u>_____ENABLE_ALL<br>
<br>
<a href="https://wiki.postgresql.org/______wiki/PostgreSQL_on_RedHat_______Linux" target="_blank">https://wiki.postgresql.org/__<u></u>____wiki/PostgreSQL_on_RedHat_<u></u>______Linux</a><br>
<<a href="https://wiki.postgresql.org/____wiki/PostgreSQL_on_RedHat_____Linux" target="_blank">https://wiki.postgresql.org/_<u></u>___wiki/PostgreSQL_on_RedHat__<u></u>___Linux</a>><span class=""><br>
<br>
<<a href="https://wiki.postgresql.org/____wiki/PostgreSQL_on_RedHat_____Linux" target="_blank">https://wiki.postgresql.org/_<u></u>___wiki/PostgreSQL_on_RedHat__<u></u>___Linux</a><br>
<<a href="https://wiki.postgresql.org/__wiki/PostgreSQL_on_RedHat___Linux" target="_blank">https://wiki.postgresql.org/_<u></u>_wiki/PostgreSQL_on_RedHat___<u></u>Linux</a>>><br>
<br>
<br>
<<a href="https://wiki.postgresql.org/____wiki/PostgreSQL_on_RedHat_____Linux" target="_blank">https://wiki.postgresql.org/_<u></u>___wiki/PostgreSQL_on_RedHat__<u></u>___Linux</a><br>
<<a href="https://wiki.postgresql.org/__wiki/PostgreSQL_on_RedHat___Linux" target="_blank">https://wiki.postgresql.org/_<u></u>_wiki/PostgreSQL_on_RedHat___<u></u>Linux</a>><br>
<br>
<<a href="https://wiki.postgresql.org/__wiki/PostgreSQL_on_RedHat___Linux" target="_blank">https://wiki.postgresql.org/_<u></u>_wiki/PostgreSQL_on_RedHat___<u></u>Linux</a><br>
<<a href="https://wiki.postgresql.org/wiki/PostgreSQL_on_RedHat_Linux" target="_blank">https://wiki.postgresql.org/<u></u>wiki/PostgreSQL_on_RedHat_<u></u>Linux</a>>>><br>
<br>
Based upon the above, it looks like you should add<br>
<br>
POSTGIS_ENABLE_OUTDB_RASTERS=1<br></span>
POSTGIS_GDAL_ENABLED_DRIVERS=_<u></u>_____ENABLE_ALL<br>
<br>
to /etc/sysconfig/pgsql/______<u></u>postgresql<span class=""><br>
<br>
The above assumes you're using the packages<br>
provided by<br>
PostgreSQL.<br>
<br></span>
<a href="http://www.postgresql.org/______download/linux/redhat/" target="_blank">http://www.postgresql.org/____<u></u>__download/linux/redhat/</a><br>
<<a href="http://www.postgresql.org/____download/linux/redhat/" target="_blank">http://www.postgresql.org/___<u></u>_download/linux/redhat/</a>><span class=""><br>
<<a href="http://www.postgresql.org/____download/linux/redhat/" target="_blank">http://www.postgresql.org/___<u></u>_download/linux/redhat/</a><br>
<<a href="http://www.postgresql.org/__download/linux/redhat/" target="_blank">http://www.postgresql.org/__<u></u>download/linux/redhat/</a>>><br>
<br>
<<a href="http://www.postgresql.org/____download/linux/redhat/" target="_blank">http://www.postgresql.org/___<u></u>_download/linux/redhat/</a><br>
<<a href="http://www.postgresql.org/__download/linux/redhat/" target="_blank">http://www.postgresql.org/__<u></u>download/linux/redhat/</a>><br>
<<a href="http://www.postgresql.org/__download/linux/redhat/" target="_blank">http://www.postgresql.org/__<u></u>download/linux/redhat/</a><br>
<<a href="http://www.postgresql.org/download/linux/redhat/" target="_blank">http://www.postgresql.org/<u></u>download/linux/redhat/</a>>>><br>
<br>
-bborie<br>
<br>
<br>
<br>
On 2/25/2015 10:10, Phil Hurvitz wrote:<br>
<br>
Hi all, I am having trouble starting PostGIS with<br>
out-db raster<br>
support<br>
<br>
In my<br></span>
/usr/local/pgsql/data/______<u></u>postgresql.conf file I<span class=""><br>
include the<br>
line<br>
<br>
POSTGIS_ENABLE_OUTDB_RASTERS=1<br>
<br>
after which PostGIS won't start (service<br>
postgresql start).<br>
<br>
Software is<br>
<br>
postgis_full_version<br>
<br>
<br></span>
------------------------------<u></u>______------------------------<u></u>--__--__--__-----------<span class=""><br>
POSTGIS="2.1.3 r12547"<br>
GEOS="3.4.2-CAPI-1.8.2 r3921"<br>
PROJ="Rel. 4.7.1,<br>
23 September 2009" GDAL="GDAL 1.11.2, released<br>
2015/02/10"<br>
LIBXML="2.7.6" TOPOLOGY RASTER<br>
<br>
<br>
Also PostGIS won't start when I specify<br>
<br></span>
POSTGIS_GDAL_ENABLED_DRIVERS=_<u></u>_____ENABLE_ALL<span class=""><br>
<br>
Any help would be appreciated!<br>
<br>
<br>
<br>
</span></blockquote>
</blockquote></div><br></div>