is there any backend (server) timeout undocumented?

Started by NunoACHenriquesalmost 24 years ago4 messagesgeneral

nach@fct.unl.pt

almost 24 years ago

Hi!

I have sended the message below to pgadmin-support (by mistake I
think) and to pgsql-hackers but receive no answers... I hope you can help me
on this...

Is there any server timeout that is undocumented?

I've issued a query like the one below and the server timed out after
120min (+/-). The query "construct_warehouse()" can last well above the
120min because it fills a table with millions of tuples... I really believe
in PostgreSQL! :-)

----------------------------------------------------------------------------
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.
!> \q
----------------------------------------------------------------------------

I've searched the archives for some documented timeout but nothing...

I've searched the postgresql.conf file and nothing...

Can anyone help me? Thanks in advance!

Note: the first time I noticed a time out was using a JDBC driver and
then I've tested in the pgsql console to confirm it.

Please reply to: nach@fct.unl.pt. I'm not a member of this list.

--
o__ Bem haja,
_.>/ _ NunoACHenriques
(_) \(_) ~~~~~~~~~~~~~~~
http://students.fct.unl.pt/users/nuno/

Doug Fields

dfields-pg-general@pexicom.com

almost 24 years ago

In reply to: NunoACHenriques (#1)

Re: is there any backend (server) timeout

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.

I had this happen to me the other day, when my server booted with only 1GB
of RAM instead of the usual 2GB. PostgreSQL started thrashing something
fierce since I give it 1.4GB of shared memory, and not too long after that
I got that same message in a JDBC SQLException.

That doesn't really help, but...

Doug

Mitch Vincent

mitch@concept-factory.com

almost 24 years ago

In reply to: Doug Fields (#2)

Re: is there any backend (server) timeout

On 5/27/02 4:18 PM, "Doug Fields" <dfields-pg-general@pexicom.com> wrote:

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.

I had this happen to me the other day, when my server booted with only 1GB
of RAM instead of the usual 2GB. PostgreSQL started thrashing something
fierce since I give it 1.4GB of shared memory, and not too long after that
I got that same message in a JDBC SQLException.

That doesn't really help, but...

Doug

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

That's a pretty standard "PostgreSQL did something bad" message, so without
more information it's hard to know what happened... Can you replicate this
crash?

-Mitch