Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eOnIt-00060Z-E3 for pgsql-docs@arkaria.postgresql.org; Tue, 12 Dec 2017 16:21:11 +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 1eOnIs-0006yr-W3 for pgsql-docs@arkaria.postgresql.org; Tue, 12 Dec 2017 16:21:10 +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 1eOnIs-0006yh-Qp for pgsql-docs@lists.postgresql.org; Tue, 12 Dec 2017 16:21:10 +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.89) (envelope-from ) id 1eOnIj-0005RW-Hj for pgsql-docs@postgresql.org; Tue, 12 Dec 2017 16:21:10 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 4EFDA216C3; Tue, 12 Dec 2017 11:20:58 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 12 Dec 2017 11:20:58 -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=MALUh/ R3QNHzV1cn/7cWFD2kmpU35dKLyBZBJPEjuIY=; b=o8A85JaBGqigRqs+L0KAEZ 6Ex2WmuhmR+NSO3KVVFGRJ6oY43jJk9MOi3r6X9DAG2hbdPwvNfPGuAMg2BUB772 67BdayO3cqMWNZ/aNlb+/nK/lijP6pj/4BNUemqmzGibhS4RGUINTziQrbLasKLy Tm0M/cl5D3Y/c/Ge7+khJvDzMrKQMbcFd3G3vhgM2fbdJ9guO0Cb8iVw9OkViuhe 7vzaAu+1E1nsVcEpyxiWIJFn2rSa2wtzdGS2ESuA7kt8dlVnnpOXSbENArPHH9lo PE4ioFzBraYthkkj7M+Gk1FsvKtCYN8ToVmqFM+VmckQzrJWTCdHYhQ0DgpBN3AQ == 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 099BF7E2E2; Tue, 12 Dec 2017 11:20:58 -0500 (EST) Subject: Re: Potentially misplaced "we trust" To: blaz@merela.org, pgsql-docs@postgresql.org References: <20171212103312.20142.33139@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Tue, 12 Dec 2017 11:20:57 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171212103312.20142.33139@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 12/12/17 05:33, blaz@merela.org wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/using-explain.html > Description: > > "(Every correct plan will output the same row set, we trust.)" > Does this sentence mean that "every correct plan will *in most cases* output > the same row set"? Or something different altogether? This is a slightly silly way of saying, if the code is correct, then every plan will output the same set of rows. I think it's OK to leave it like that. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services