Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1efPOO-0000er-6T for pgsql-docs@arkaria.postgresql.org; Sat, 27 Jan 2018 12:15:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1efPOL-0005TE-SG for pgsql-docs@arkaria.postgresql.org; Sat, 27 Jan 2018 12:15:29 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1efPOL-0005T4-JS for pgsql-docs@lists.postgresql.org; Sat, 27 Jan 2018 12:15:29 +0000 Received: from mail-qt0-x233.google.com ([2607:f8b0:400d:c0d::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1efPOD-00076a-W9 for pgsql-docs@postgresql.org; Sat, 27 Jan 2018 12:15:27 +0000 Received: by mail-qt0-x233.google.com with SMTP id l20so7394360qtj.11 for ; Sat, 27 Jan 2018 04:15:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=weNEoVZxKmXb/lNXsNDJy1bMiyOVsrdWZEYJq0msVak=; b=2LNcQz+hy4d0SIsw3VEP5ifmQUD9Lo1to/uFSPt7pcrE6NuLzrV43SM0zIgyUrnmLq Jy66r3tGONTzq+o9nsb0Ne6uuuJIm1oinAtDjFv+4wDVEwU/H941KmEmA7JRk8Fudp3x kApCq09BHeHa9oncUyL1HZRon3UPOGVHOuwRuAraGfJLGpoRB3JP+Yl8XRH6FkAreJFC CrgreVe/HYMArk4DsL0km1R3Bmj28Ef0jZS9FB4AFUgZev+z01gqq+KftQz/rL1S0rS5 dOEDshOMra5n3P5NE3ymzFTodoZwCWGfTi4Luz2GsbwXeK0SNtseQNVJk+jrK2s2ZWOm fYtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=weNEoVZxKmXb/lNXsNDJy1bMiyOVsrdWZEYJq0msVak=; b=GN3HWtem4XmWAjBVajMGRQbFLBQgLespR0/iK3lhLJwEZOVhVzGUio/d4kjdoobvUH Sf71IfrxkHHz+utAQ2rfoQZSpVuCIXlBRQKlFNoMbi1yYNx3CgE1izULOHrDSu7UZ+s9 T2jjreKsaDjHRAaEOF7XfGAteBLUMiai2XMDhbWf4EGcaP/8qLK73dFV3kOZpTe7LNqZ IDZ4v7QaZyx5ZNu49o/qkKXQhksz1Ym0tGykib9wrcbjWOk+BS4ISwEx0uvJNjwDJwzU tGSk64r1vaKqROincYF6aG8pjw34BTQ3zoymyuw17eUK05NqzSU6Td9KOAwZjxi2TSyF R4hg== X-Gm-Message-State: AKwxytco3uNhfpSETpKq3JE6B0uTO+81bqMU2djC7ulBG9EDQP3Lw849 tB1PhMZDkR5i7tpi31qhLQXZAbm0yY7NIAZWRgRKJ1kh X-Google-Smtp-Source: AH8x227NgouFJcUvF3EOwvWUrH2nwSqml0NsNZM0zjY1KXuNbSTO/blkTmneyFrGCaFe3X5HOpCGaJFoFclQSZtOvfA= X-Received: by 10.200.81.154 with SMTP id c26mr29181834qtn.129.1517055320927; Sat, 27 Jan 2018 04:15:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.48.123 with HTTP; Sat, 27 Jan 2018 04:15:20 -0800 (PST) In-Reply-To: References: From: Magnus Hagander Date: Sat, 27 Jan 2018 13:15:20 +0100 Message-ID: Subject: Re: Trailing semicolons on partitioning example commands To: Daniel Gustafsson Cc: pgsql-docs Content-Type: multipart/alternative; boundary="f4f5e806c44082443c0563c0f759" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --f4f5e806c44082443c0563c0f759 Content-Type: text/plain; charset="UTF-8" On Fri, Jan 26, 2018 at 3:27 PM, Daniel Gustafsson wrote: > Is there a reason for not ending all partitioning commands with semicolons > in > the declarative partitioning example? > > https://www.postgresql.org/docs/devel/static/ddl-partitioning.html > > The two last commands with TABLESPACE clauses are ended with semicolons, > the > first three arent. Attached patch adds semicolons such that all are > properly > ended. > I cant see one, since all the other examples do. Thus, pushed. Thanks! -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --f4f5e806c44082443c0563c0f759 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jan 26, 2018 at 3:27 PM, Daniel Gustafsson &l= t;daniel@yesql.se&= gt; wrote:
Is there a reason for n= ot ending all partitioning commands with semicolons in
the declarative partitioning example?

=C2=A0 =C2=A0 =C2=A0 =C2=A0 https:= //www.postgresql.org/docs/devel/static/ddl-partitioning.html<= br>
The two last commands with TABLESPACE clauses are ended with semicolons, th= e
first three arent.=C2=A0 Attached patch adds semicolons such that all are p= roperly
ended.

I cant see one, since all the ot= her examples do.

Thus, pushed. Thanks!=C2=A0
=


--
=C2=A0Magnus Hag= ander
=C2=A0Me: h= ttps://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/
--f4f5e806c44082443c0563c0f759--