Greg Sabino Mullane wrote:
> A use case would be dumping a large table and wanting to
> load it into the database, but wanting to stop the job if it
> is still running an hour from now, when a maintenance window
> is scheduled to start.
statement_timeout is pretty useless for that purpose, because it limits
the time on a per-statement basis. It would cancel the COPY of any
tables larger than X, but if you have multiple tables (a partitioned
table, perhaps) just below the threshold, they would all be dumped even
though the cumulative time is well beyond statement_timeout.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
