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 15FAA3A19D5 for ; Fri, 14 Jan 2005 12:03:23 +0000 (GMT) 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 58747-03 for ; Fri, 14 Jan 2005 12:03:18 +0000 (GMT) Received: from laptop.kieser.net (kieser2.demon.co.uk [80.176.229.121]) by svr1.postgresql.org (Postfix) with ESMTP id 4BA583A199E for ; Fri, 14 Jan 2005 12:03:12 +0000 (GMT) Received: from [127.0.0.1] (laptop.kieser2.demon.co.uk [127.0.0.1]) by laptop.kieser.net (Postfix) with ESMTP id 45B8018333 for ; Fri, 14 Jan 2005 12:03:39 +0000 (GMT) Message-ID: <41E7B4F6.8070505@kieser.net> Date: Fri, 14 Jan 2005 12:03:02 +0000 From: Bradley Kieser User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en, en-us MIME-Version: 1.0 To: PgSQL ADMIN Subject: Script terminates even though ON_ERROR_STOP not set Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.331 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/143 X-Sequence-Number: 16002 I have an admin script that drops a schema and then recreates it (quick way to refresh from backup). However, if the schema doesn't exist, the drop errors, as you would expect. The next SQL command, the schema create, is never executed. I do not have ON_ERROR_STOP set so why is this happening? I don't want to split down to two calls of psql if possible, which is the present work-around. Would prefer to solve the problem. Thanks, Brad