Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 980EF6341BE for ; Thu, 27 May 2010 03:21:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 50913-01 for ; Thu, 27 May 2010 06:20:58 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 02FA1632538 for ; Thu, 27 May 2010 03:20:57 -0300 (ADT) Received: from webserv.wug.de ([194.25.154.138]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0Lj72Q-1Neb8r17Us-00caV9; Thu, 27 May 2010 08:20:55 +0200 Received: from kretschmer by webserv.wug.de with local (Exim 3.36 #1) id 1OHWSc-0003Mr-00 for pgsql-sql@postgresql.org; Thu, 27 May 2010 08:20:54 +0200 Date: Thu, 27 May 2010 08:20:54 +0200 From: "A. Kretschmer" To: pgsql-sql@postgresql.org Subject: Re: Rules and sequences Message-ID: <20100527062052.GA6907@a-kretschmer.de> References: <20100526181620.GA54996@osiris.mauzo.dyndns.org> <4884.1274918674@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4884.1274918674@sss.pgh.pa.us> X-OS: Debian/GNU Linux - weil ich es mir Wert bin! User-Agent: Mutt/1.5.9i X-Provags-ID: V01U2FsdGVkX1/Y0qnc8X7SiZBI2zgvNUJZvBJLXj2chLvna9J IDlCoiQA3bWfEnHCTDJbamCwWWxTx0PdqF/RwsEE68J0swt9U1 hRqtP5VsXIwriz4HPug7A== X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.81 tagged_above=-5 required=5 tests=BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, T_FRT_CONTACT=0.01 X-Spam-Level: X-Archive-Number: 201005/121 X-Sequence-Number: 34169 In response to Tom Lane : > Ben Morrow writes: > > I am trying to implement a fairly standard 'audit table' setup, but > > using rules instead of triggers (since it should be more efficient). > > Rules are sufficiently tricky that I would never, ever rely on them for > auditing. Use a simple AFTER trigger instead. There are a ready solution: http://andreas.scherbaum.la/blog/archives/100-Log-Table-Changes-in-PostgreSQL-with-tablelog.html Regards, Andreas -- Andreas Kretschmer Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header) GnuPG: 0x31720C99, 1006 CCB4 A326 1D42 6431 2EB0 389D 1DC2 3172 0C99