Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dnxo7-0000QE-6i for pgsql-docs@arkaria.postgresql.org; Sat, 02 Sep 2017 02:05:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dnxo6-0000wO-Pg for pgsql-docs@arkaria.postgresql.org; Sat, 02 Sep 2017 02:05:10 +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 1dnxni-0000FM-UI for pgsql-docs@postgresql.org; Sat, 02 Sep 2017 02:04:47 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dnxnX-0003I4-OA for pgsql-docs@postgresql.org; Sat, 02 Sep 2017 02:04:45 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id E777D20BA1; Fri, 1 Sep 2017 22:04:34 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 01 Sep 2017 22:04:34 -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=+OlLFxtijdZqaT/U6j7qah1ZpxUHARg8/L0lrqfYiXs=; b=jZ2xz4BR kPbgp+OxohSqb3aPHBDtSL615NWnuNq4cwADs/ufazK/DEvbzO1ZB+ccEH9K6D81 OCEu8u493Gj8oDjRiYGm9DFwCu5ovgTV2dnY63cFj2NyCsL5yuSQR3C42Xzhn/qv +6Iu4GgoqsSVsnAekcI57aHwLUPknJjW7UBONp+HW5mw0OssuahqKGjix265xEFF 8vGz8rwpIV0wnyRxVaqXrFxlkn6CDUgkSXD6FMVKAJ15XaObMhNevrhf7iuYUQma Tzq4ncIZEL23zW2VUq49V6Gcco/+bYfeKGBBGx2zFvSX5cOeRE9urvZy9YCmnd+s 0qrygAbzQnyzWA== X-ME-Sender: X-Sasl-enc: UGqBqUOiMWfLTN4Bv0zssRFhTDQ7CalY8Z8uoYQT1xqJ 1504317874 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 89E687E7AD; Fri, 1 Sep 2017 22:04:34 -0400 (EDT) Subject: Re: Mistype To: splarv@ya.ru, pgsql-docs@postgresql.org References: <20170827093000.8143.95191@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <416f6dba-2683-0aec-bd44-1506a3dc43df@2ndquadrant.com> Date: Fri, 1 Sep 2017 22:04:32 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170827093000.8143.95191@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 8/27/17 05:30, splarv@ya.ru wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-createpolicy.html > Description: > > "Note that INSERT with ON CONFLICT DO UPDATE checks INSERT policies' WITH > CHECK expressions only for rows appended to the relation by the INSERT > path." > > May be "by the INSERT part"? No this is correct. The ON CONFLICT documentation frequently speaks of an "UPDATE path" and an "INSERT path" that the command may end up taking. -- 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