Re: CREATE TABLE .. LIKE .. EXCLUDING documentation - Mailing list pgsql-hackers

From Yugo Nagata
Subject Re: CREATE TABLE .. LIKE .. EXCLUDING documentation
Date
Msg-id 20180629161415.c0f4e574.nagata@sraoss.co.jp
Whole thread Raw
In response to Re: CREATE TABLE .. LIKE .. EXCLUDING documentation  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: CREATE TABLE .. LIKE .. EXCLUDING documentation
List pgsql-hackers
On Fri, 29 Jun 2018 08:39:01 +0200
Daniel Gustafsson <daniel@yesql.se> wrote:

> > On 29 Jun 2018, at 07:56, Yugo Nagata <nagata@sraoss.co.jp> wrote:
> > On Thu, 28 Jun 2018 16:22:15 -0700
> > "David G. Johnston" <david.g.johnston@gmail.com> wrote:
>
> >> ​Maybe try something like:
> >>
> >> It is legal to specify the same option multiple times - e.g., "INCLUDING
> >> option EXCLUDING option" - the outcome is whichever comes last in the
> >> command (i.e., in the example, option is excluded).
> >
> > Certainly. However, it seems to me that example is also redundant.
> > I rewrote this as follows:
> >
> > It is legal to specify multiple options for the same kind of object.
> > If they conflict, latter options always override former options.
> >
> > Does this make sense?
>
> I think this wording makes sense and is clear. Only found a small typo:
>
> +      This is tipically used after <literal>INCLUDING ALL</literal>.
>
> s/tipically/typically/

Thanks a lot.

I updated the patch.

>
> cheers ./daniel


--
Yugo Nagata <nagata@sraoss.co.jp>

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: partitioning - changing a slot's descriptor is expensive
Next
From: Yugo Nagata
Date:
Subject: Re: Forbid referencing columns by names in ALTER INDEX ... SETSTATISTICS