Skip site navigation (1) Skip section navigation (2)

Re: is there any backend timeout undocumented?

From: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>
To: NunoACHenriques <nach(at)fct(dot)unl(dot)pt>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: is there any backend timeout undocumented?
Date: 2002-05-27 22:28:22
Message-ID: m3k7ppted5.fsf@conexa.fciencias.unam.mx (view raw or flat)
Thread:
Lists: pgsql-hackers
NunoACHenriques <nach(at)fct(dot)unl(dot)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.

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2002-05-28 01:00:43
Subject: Re: [HACKERS] Re : Solaris Performance - 64 bit puzzle
Previous:From: Christopher Kings-LynneDate: 2002-05-27 22:11:38
Subject: Re: SRF rescan testing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group