Frank Bax <fbax@sympatico.ca> writes:
> Script and database are both on same system. Faster system was able
> to get past next database access. So far so good, script continues
> to run. Still curious why it failed on slower system, though.
There's no connection timeout built into PG itself. The message implies
that something sent the backend a SIGTERM signal, which makes me wonder
if you are running the postmaster under ulimit settings that include
a finite limit on process CPU or I/O expenditure. Some platforms have
special signals for that (SIGXCPU etc) but I think some just send
SIGTERM when a process goes over the limit.
regards, tom lane