Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dgGmT-00059N-SD for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 20:43:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dgGmT-0006RJ-8R for pgsql-docs@arkaria.postgresql.org; Fri, 11 Aug 2017 20:43:41 +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 1dgGmS-0006Qa-F2 for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 20:43:40 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dgGmO-0008OH-QL for pgsql-docs@postgresql.org; Fri, 11 Aug 2017 20:43:39 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0A56120E69; Fri, 11 Aug 2017 16:43:35 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Fri, 11 Aug 2017 16:43:35 -0400 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:x-sasl-enc; s= fm1; bh=5L+ETwEjbXP4EriEEtZE4UTV4on51sQOVeGw5Fgldog=; b=QoCtSfhx dbcrg5fX/TMLjgR3lQ87PgU5tcYU+HDGezAnlg8HlIr30XVSnW7raOoeUEDfqDNs dnF+WB25QQfNndGk+G2IRIGZZ6hlNN3UAFb6hBWatRjLByf8CmvhoKoBMdtwO15l Xvr+KotBa13lCWejDgPTxXTzRuMjgbWlXAFah/7jupr3bGvSWXB70h8BySfB/caX Qw1Wd5q4LCYafZVAK830vuQmCmg2a/Z2sJPUhd7/unQXpkV031RP+lRZ4sDtW2AD IDfacDvCQ9vAaQECDixvCmh7QmOCFl2UhmvLPC9vqSWopmZ59Uc9062M5PK0LNZk qTjrSADEWMaxCg== X-ME-Sender: X-Sasl-enc: 1P2D4aLTPI5nRgPaAUdDYzbrc1F9uTET54gIC66KbRyK 1502484214 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 BA110241D9; Fri, 11 Aug 2017 16:43:34 -0400 (EDT) Subject: Re: Improve docuemntation for cidr/inet To: kes-kes@yandex.ru, pgsql-docs@postgresql.org References: <20170422081914.24368.32804@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Fri, 11 Aug 2017 16:43:34 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170422081914.24368.32804@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 4/22/17 04:19, kes-kes@yandex.ru wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/datatype-net-types.html > Description: > > >The essential difference between inet and cidr data types is that inet > accepts values with nonzero bits to the right of the netmask, whereas cidr > does not. > > May you please provide example to see the difference visually. I do not > understand that sentence completely I have added an example to the version 10 documentation. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs