X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A2CB252C2C for ; Wed, 17 Aug 2005 18:40:45 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26674-10 for ; Wed, 17 Aug 2005 21:40:43 +0000 (GMT) Received: from bedrock.cromagnon.com (170-215-19-8.dsl1.mnd.mn.frontiernet.net [170.215.19.8]) by svr1.postgresql.org (Postfix) with ESMTP id 8263652BA9 for ; Wed, 17 Aug 2005 18:40:39 -0300 (ADT) Received: from lt-cservin.cdhps.com (cservin.dsl.visi.com [209.98.143.247]) (authenticated bits=0) by bedrock.cromagnon.com (8.12.8/8.12.8) with ESMTP id j7HLeerF028534 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 17 Aug 2005 16:40:42 -0500 From: Craig Servin Organization: Cro-Magnon To: pgsql-admin@postgresql.org Subject: Re: Updateing pg_trigger and pg_constraint Date: Wed, 17 Aug 2005 16:40:41 -0500 User-Agent: KMail/1.8.1 Cc: Tom Lane References: <200508161521.23802.cservin@cromagnon.com> <7767.1124311218@sss.pgh.pa.us> In-Reply-To: <7767.1124311218@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508171640.41924.cservin@cromagnon.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 required=5 tests=[FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200508/232 X-Sequence-Number: 18551 > Try starting a fresh backend session. Manual hacking of those tables > isn't going to cause a relcache reload ... > Simply reconnecting to the backend does not help. If I restart the server everything works as expected. I am wondering if there is a way to trigger a relcache reload without shutting down the PostgreSQL. Craig