Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id E57DB1337B58;
	Mon,  7 Mar 2011 17:02:43 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 43005-04; Mon,  7 Mar 2011 21:02:33 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id B6C74133616B;
	Mon,  7 Mar 2011 17:02:32 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p27L2UpC013447;
	Mon, 7 Mar 2011 16:02:30 -0500 (EST)
To: Thom Brown <thom@linux.com>
cc: Robert Haas <robertmhaas@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Column-level trigger doc typo fix 
In-reply-to: <AANLkTimX=n2P4G=p+x-qu02u=SuYfv+WXsh6jAmuJrv3@mail.gmail.com> 
References: <AANLkTikTHrxO++5gW5VBiMiUN2+hpRtPaj_C4BXGY6yp@mail.gmail.com>
	<AANLkTikAFXQXqm8H9drXfEFmgDnNGtVNHT70tmXVgGB6@mail.gmail.com>
	<AANLkTimX=n2P4G=p+x-qu02u=SuYfv+WXsh6jAmuJrv3@mail.gmail.com>
Comments: In-reply-to Thom Brown <thom@linux.com>
	message dated "Mon, 07 Mar 2011 23:29:06 +0530"
Date: Mon, 07 Mar 2011 16:02:30 -0500
Message-ID: <13446.1299531750@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201103/31
X-Sequence-Number: 6464

Thom Brown <thom@linux.com> writes:
> On 7 March 2011 22:39, Robert Haas <robertmhaas@gmail.com> wrote:
>> That's not really a typo so much as a think-o, I think.  Maybe a
>> little more text would help clarify: A column-specific trigger (one
>> defined using the <literal>UPDATE OF
>> <replaceable>column_name</replaceable></literal> syntax) will fire
>> when...
>> 
>> It should really go on to say... "where event can be one of...", like
>> EXPLAIN and COPY do, shouldn't it?  Otherwise it's pretty hard to tell
>> what you should put there without looking up the main docs.

> Yes, absolutely.  In fact that's what I was looking for when I first
> visited that page.

Applied both of these changes along with a bit of markup cleanup.

			regards, tom lane