Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XoByF-0004GF-OM for pgsql-general@arkaria.postgresql.org; Tue, 11 Nov 2014 13:59:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XoByE-0004CX-5Q for pgsql-general@arkaria.postgresql.org; Tue, 11 Nov 2014 13:58:58 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XoByC-0004CL-S9 for pgsql-general@postgresql.org; Tue, 11 Nov 2014 13:58:57 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XoBy8-0007I2-IB for pgsql-general@postgresql.org; Tue, 11 Nov 2014 13:58:54 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5A8EB200CA for ; Tue, 11 Nov 2014 08:58:51 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 11 Nov 2014 08:58:51 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= x-sasl-enc:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=EA4ALLBc5iZrnaPCDkQun7lqfUU=; b=lcAwGGfHRZcbsE7K8L DOaBW1LV7VCgr6ndANc6XLysO0taCrNa8z+FJVo2DjEKzBe6/8Ny/jP/cnIULV6j OVpybnfxB5dMZEG5sgFtF62xL3im2UPJEpn07YAv+MTaMtelEg67o4sFH/CO0udE ySTpsg0sGbPYSb4m6teaf5Avw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:message-id:date:from :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=EA4ALLBc5iZrnaPCDkQun7 lqfUU=; b=SvvLdUwVeiLbOGiagLnzINDV3oW08V/ilOSkgrkJcTMWPmWiwaJhUI R74u2DydWMjImxjGIN97U8OExi7/cQaXaPu6Fl/bU2NDWyrcgcWOoW1X9e+YJsJG gzqTRWJTBgHVuRGTrESidi3P3oXA6Tb6JjtD3DHE3opn+swZiP4Vc= X-Sasl-enc: T84ZVc3VJtqEp0krGbRzRJS+cH6ExO+xX5rgW11zDX26 1415714331 Received: from [192.168.1.2] (unknown [174.21.91.221]) by mail.messagingengine.com (Postfix) with ESMTPA id B6C1DC00013; Tue, 11 Nov 2014 08:58:50 -0500 (EST) Message-ID: <54621619.2040505@aklaver.com> Date: Tue, 11 Nov 2014 05:58:49 -0800 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: avpro avpro , pgsql-performance@postgresql.org, pgsql-general@postgresql.org Subject: Re: trigger Before or After References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 11/10/2014 10:38 PM, avpro avpro wrote: > hi, > > in the pgsql documentation > (http://www.postgresql.org/docs/9.1/static/sql-createtrigger.html) > > i haven't seen anything referring to: how is affected the data inserted > in the new table by a trigger Before Insert compared with a trigger > After Insert? and anything related to performance See bottom of above page and here: http://www.postgresql.org/docs/9.1/static/trigger-definition.html > > thank you > have a sunny day > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general