X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 809C353C09 for ; Fri, 1 Apr 2005 04:52:52 +0100 (BST) 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 27552-06 for ; Fri, 1 Apr 2005 03:52:49 +0000 (GMT) Received: from metux.de (seven.metux.de [193.16.1.1]) by svr1.postgresql.org (Postfix) with ESMTP id 3B48653C1E for ; Fri, 1 Apr 2005 04:52:46 +0100 (BST) Received: (from weigelt@localhost) by metux.de (8.12.10/8.12.10) id j313qnCv027921 for pgsql-sql@postgresql.org; Fri, 1 Apr 2005 05:52:49 +0200 Date: Fri, 1 Apr 2005 05:52:49 +0200 From: Enrico Weigelt To: pgsql-sql Subject: asynchrous triggers Message-ID: <20050401035249.GA23298@nibiru.borg.metux.de> Reply-To: weigelt@metux.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/2 X-Sequence-Number: 20895 hi folks, is it possible somehow to make (AFTER) triggers run in their own process/thread, so the calling session can return immediately and the trigger runs in background ? thx -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: contact@metux.de cellphone: +49 174 7066481 --------------------------------------------------------------------- -- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops -- ---------------------------------------------------------------------