| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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:53:20 |
| Message-ID: | 20180131225320.GB10514@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 31, 2018 at 05:13:41PM -0500, Robert Haas wrote:
> On Wed, Jan 31, 2018 at 5:00 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > doc: clarify 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.
Thanks, fixed. I struggled with that word.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2018-02-01 13:30:53 | pgsql: psql: Add quit/help behavior/hint, for other tool portability |
| Previous Message | Bruce Momjian | 2018-01-31 22:52:57 | pgsql: doc: fix trigger inheritance wording |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2018-01-31 23:19:25 | Re: WINDOW RANGE patch versus leakproofness |
| Previous Message | Bruce Momjian | 2018-01-31 22:51:51 | Re: proposal: alternative psql commands quit and exit |