Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 474B664FCD2 for ; Fri, 12 Sep 2008 18:07:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 41511-03 for ; Fri, 12 Sep 2008 18:07:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 3930564FCCC for ; Fri, 12 Sep 2008 18:07:25 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-19-82.bk17-dsl.surnet.cl [190.95.19.82]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m8CLAgpB024766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Sep 2008 14:10:45 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id C141747CAB; Fri, 12 Sep 2008 17:07:17 -0400 (CLT) Date: Fri, 12 Sep 2008 17:07:17 -0400 From: Alvaro Herrera To: kevin kempter Cc: pgsql-admin@postgresql.org Subject: Re: Triggers & BLOB's Message-ID: <20080912210717.GP8854@alvh.no-ip.org> References: <1C560AEB-0265-4021-B60C-2F20D1971126@kevinkempterllc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1C560AEB-0265-4021-B60C-2F20D1971126@kevinkempterllc.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Fri, 12 Sep 2008 14:10:45 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/127 X-Sequence-Number: 30220 kevin kempter wrote: > Hi All; > > Can I put an update/insert/delete trigger on a BLOB (lo_* style) column, > It looks like the trigger should actually live on the data column of the > pg_largeobject table to be effective. Is this correct ? You can't put a trigger in pg_largeobject. Of course, you can put a trigger in the table that you're storing the OID's in. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support