Received: from sss.pgh.pa.us (sss-backup.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9UKZGP36679 for ; Tue, 30 Oct 2001 15:35:16 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9UKYrc02367; Tue, 30 Oct 2001 15:34:53 -0500 (EST) To: sharmad@goatelecom.com cc: pgsql-sql@postgresql.org Subject: Re: postgresql error In-reply-to: <3bdd7ba0.77a.0@punweb01> References: <3bdd7ba0.77a.0@punweb01> Comments: In-reply-to sharmad@goatelecom.com message dated "Mon, 29 Oct 2001 21:24:08 +0550" Date: Tue, 30 Oct 2001 15:34:52 -0500 Message-ID: <2364.1004474092@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/422 X-Sequence-Number: 5373 sharmad@goatelecom.com writes: > Is there anyway to increase the query time in postgresql > because if the query is long and so is the database then the pgRead > error occurs resulting in the break of connection with the database > and recently also giving me problems in taking backups. There is no query timeout in Postgres. How about telling us exactly what you're doing and what symptoms you see, instead of jumping to a conclusion about the cause? regards, tom lane