Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cvcSN-0003MI-W4 for pgsql-docs@arkaria.postgresql.org; Wed, 05 Apr 2017 04:22:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cvcSN-0004ol-9H for pgsql-docs@arkaria.postgresql.org; Wed, 05 Apr 2017 04:22:07 +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 1cvcS0-00048a-7r for pgsql-docs@postgresql.org; Wed, 05 Apr 2017 04:21:44 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cvcRx-00049F-PP for pgsql-docs@postgresql.org; Wed, 05 Apr 2017 04:21:43 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 223F82091F; Wed, 5 Apr 2017 00:21:40 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 05 Apr 2017 00:21:40 -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=2KlvHtfTNjRwld+KMrjQ+4qpC+GwXHvZ3+DygLiWUYw=; b=sNSwC3nn MmaG9nSdUjgc9qZuVxDe1YfXLo2i9vvR+XvOgF3z8KH8mBuv2x+Lt+yeHGGTVO49 /TgBRpjXpu7SUrQnfCWy96kChEU25UgkonuhI0Q4aVf3BasMvIscJf+2niZHKumr nWe79t45ORcBU4BrhVQtZynr/vgxaIBU+BjwboqjPUM+MwZjzw5fnCLeSgmTD7VZ EGf+dLLka7ZKOdI/6kMLOfWm/ZkWJVeViqVWo6JYnThNxMjmPxC7xcrtsFs48Jlp gMIi2mUrM6zW3mZkiBXiKDGpGOyltnhdNoBSN3C8uqaeGjYBWnkn6TsaZQ+Es7kZ hjE066qd257M5A== X-ME-Sender: X-Sasl-enc: G0M8AsTw8SI7w8cUEPOKr/Sid9cApfh7jdW61d6oMq5S 1491366099 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 DBD917E1DC; Wed, 5 Apr 2017 00:21:39 -0400 (EDT) Subject: Re: Cross-references between DOMAIN and POLICY To: postgresql@eric.brechemier.name, pgsql-docs@postgresql.org References: <20170202205409.1407.26902@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <64a81a19-0ed0-d1c7-8ea2-27ff04bdd0a5@2ndquadrant.com> Date: Wed, 5 Apr 2017 00:21:39 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170202205409.1407.26902@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 2/2/17 15:54, postgresql@eric.brechemier.name wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-createpolicy.html > Description: > > Domains and row level policies are similar in the definition of a constraint > with a CHECK expression. > > There should be a mention of domains on the page `CREATE POLICY` and an > explanation of the differences between domains and policies in the > discussion of `Row Security Policies`. > > There should be a mention of policies on the page `CREATE DOMAIN`. I don't think they are that similar, other than that the word CHECK appears in their syntax. -- 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