X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 6F9C0D1B447 for ; Sat, 17 Jan 2004 00:57:54 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28783-09 for ; Fri, 16 Jan 2004 20:57:26 -0400 (AST) Received: from mail.securitylending.com (mail.securitylending.com [65.90.55.69]) by svr1.postgresql.org (Postfix) with ESMTP id D92F7D1B44A for ; Fri, 16 Jan 2004 20:57:21 -0400 (AST) Subject: setting statement_timeout on live postmaster From: Warren Little To: pgsql-admin@postgresql.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1074301044.5871.32.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 16 Jan 2004 17:57:24 -0700 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/159 X-Sequence-Number: 12022 Is there anyway to modify the statement_timeout value set in postgresql.conf we creating a connection? I would like to have the value set to something like 60 seconds on a regular basis but my vacuumdb statements run longer and timeout without completing the vacuum -- Warren Little Senior Vice President Secondary Marketing Security Lending Wholesale, LC www.securitylending.com Tel: 866-369-7763 Fax: 866-849-8082