From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thom Brown <thom@linux.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Column-level trigger doc typo fix
Date: Mon, 07 Mar 2011 16:02:30 -0500
Message-ID: <13446.1299531750@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, thom@linux.com, robertmhaas@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: Column-level trigger doc typo fix
In-Reply-To: <13446.1299531750@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox