Re: is there any backend timeout undocumented?

NunoACHenriques <nach@fct.unl.pt> writes:

>     I've issued a query like the one below and the server timed out after 
> 180min (+/-). The query "construct_warehouse()" can last well above the 
> 180min because it fills a table with millions of tuples...
> 
> ----------------------------------------------------------------------------
> spid=> vacuum full analyze ; select construct_warehouse() ; vacuum analyze ;
> NOTICE:  Skipping "pg_group" --- only table or database owner can VACUUM it
> NOTICE:  Skipping "pg_database" --- only table or database owner can VACUUM it
> NOTICE:  Skipping "pg_shadow" --- only table or database owner can VACUUM it
> VACUUM
> server closed the connection unexpectedly
>     This probably means the server terminated abnormally
>     before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> You are currently not connected to a database.

As the message says the backend is not "timing out"; it's terminating
*abnormally*, What's doing the construct_warehouse() function?, It's
written in C?, Could you send the backtrace from the core file?

Regards,
Manuel.