Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ed1b5-00039x-3G for pgsql-docs@arkaria.postgresql.org; Sat, 20 Jan 2018 22:26:47 +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 1ed1b3-00050E-MM for pgsql-docs@arkaria.postgresql.org; Sat, 20 Jan 2018 22:26:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ed1b3-000505-99 for pgsql-docs@lists.postgresql.org; Sat, 20 Jan 2018 22:26:45 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ed1az-0003eF-HC for pgsql-docs@lists.postgresql.org; Sat, 20 Jan 2018 22:26:44 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6B4EF20C6F; Sat, 20 Jan 2018 17:26:38 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Sat, 20 Jan 2018 17:26:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=SsLBqP 7EXt+Nwr/piQhYeznd2QOLCA5gKxsXd9zb45g=; b=ml5K7gsYrvj/hgIkjYs9cx d9TQEyxy9tqrKzV8le8eE1ZNgjHpHgJUJLEWvo7gxPolfoEg6hqHN4Mc6E28+UJQ pMtJVuPQKiPPhcdibpVpLxBJfZi+JpK7y8PohXIl66wNPW3q2pwuZaGBujWM/e1u 25q0+ymJ/89aQEiNk4sXsabkS42sY52Qr0B2YuHWGAfZaqtTnpuhMnw5Tg0baBd2 0zT5N1ot7LTyFozVD20UhNW8uPgwrbR4u9N6kEaiqxRIkG5acaUIY6s09QTwlLyH /4rn0uwPE/7g/sAKkj4n877arP/WiVzRRNI40F3kVkdExgNEtHRc8rycpd6v/V9g == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 26FEC2418B; Sat, 20 Jan 2018 17:26:38 -0500 (EST) Subject: Re: overlapping ranges To: nicholas.farrell@gmail.com, pgsql-docs@lists.postgresql.org, PG Doc comments form References: <20180120205832.3624.66654@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Sat, 20 Jan 2018 17:26:37 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180120205832.3624.66654@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 1/20/18 15:58, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/ddl-partitioning.html > Description: > > In the date partitioning example the first and last dates are the first of > the month, which will cause conflicts. The last date needs to be the final > day of the same month. I don't think so, because the upper bound of the range is not included in the range. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services