With long running processes, time-out could be an issue.
Has anyone got experience in creating a "Keep alive script" solution to
share?
Regards,
Shao
___
postgis-users mailing list
postgis-users@lists.osgeo.org
On 1/13/2020 6:10 AM, Shaozhong SHI wrote:
With long running processes, time-out could be an issue.
Has anyone got experience in creating a "Keep alive script" solution
to share?
Need more information.
What is timing out? ssh, php, psql, etc?
___
Hi Giuseppe,
Here is the original explain output (You can also get this from clicking on
the "Source" tab in the Depsez links):
9.6
HashAggregate (cost=42103.26..42105.26 rows=200 width=16) (actual
time=94062.150..94062.161 rows=59 loops=1)
Group Key: (st_valuecount(cv.rast, 1, true,
Psql may carry out large queries on big data sets. These operations may
take a long time to complete. It occurs that psql loses connection to the
database.
When a do loop is created to limit queries to range of rows at a time,
engagement between psql and postures can be maintained. However,
Apology. I refer to postgres,. But my phone made it something else.
On Monday, 13 January 2020, Shaozhong SHI wrote:
> Psql may carry out large queries on big data sets. These operations may
> take a long time to complete. It occurs that psql loses connection to the
> database.
>
> When a do
On 1/13/2020 5:28 PM, Shaozhong SHI wrote:
Psql may carry out large queries on big data sets. These operations
may take a long time to complete. It occurs that psql loses
connection to the database.
When a do loop is created to limit queries to range of rows at a time,
engagement between
Hi,
I'm learning to use PostGIS with PostgreSQL by way of the book _PostGIS
In Action, 2ed_. I'm working in Windows 10. Using the following example
from the book:
CREATE TABLE ch02.my_rasters (
rid serial PRIMARY KEY,
name varchar(100),
rast raster);
I get the error in the
