| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: doc: clearify trigger behavior for inheritance |
| Date: | 2018-01-31 22:13:41 |
| Message-ID: | CA+TgmoZACVK0TKKzW=P0+A78nq3Lm8fFh_hfvqqtOYRAogd1sQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 31, 2018 at 5:00 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> doc: clearify trigger behavior for inheritance
>
> The previous wording added in PG 10 wasn't specific enough about the
> behavior of statement and row triggers when using inheritance.
This may be a good change in general, but the change of "affected" to
"effected" is bad English.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-01-31 22:52:57 | pgsql: doc: fix trigger inheritance wording |
| Previous Message | Bruce Momjian | 2018-01-31 22:10:09 | pgsql: doc: clarify major/minor pg_upgrade versions with examples |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2018-01-31 22:17:35 | [WIP PATCH] Index scan offset optimisation using visibility map |
| Previous Message | Bruce Momjian | 2018-01-31 22:00:28 | pgsql: doc: clearify trigger behavior for inheritance |