Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oZBo9-0004Cm-Sb for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Sep 2022 13:55:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oZBo8-0005lE-Nn for pgsql-hackers@arkaria.postgresql.org; Fri, 16 Sep 2022 13:55:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oZBo7-0005k8-UY for pgsql-hackers@lists.postgresql.org; Fri, 16 Sep 2022 13:55:04 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oZBo3-00050a-IQ for pgsql-hackers@postgresql.org; Fri, 16 Sep 2022 13:55:02 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id DFB865C026D; Fri, 16 Sep 2022 09:54:56 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 16 Sep 2022 09:54:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1663336496; x= 1663422896; bh=KRecXkYfVJfgYiPDf45DR1mKe5Ua62ZXZ0S0NR4rE/o=; b=D j8ngzrNFHvf1bfBzbxbLxggyODNP1x0iLpvNDCq0xKMpK1Mn90y3ja7TV8bA+gm5 2gxA79NVSAod5Cvyb7EZDo8ITBl2bIL4iQ9sxXI0HKXckYVumYEel90dTDzhs8Z2 YchpQNNPSGVCCFjB3uFtzzT7LAsVYu3cDYkSCcaVcnFGgTLr+1DTEWnggeNjEvJ4 dN3vM6s7BCkmkxOxWYCRAlpbM/pg20DAEhw2/xFkfTW7JwxAK52gLY7agtaFdeB7 uTpN4Hs7PQoIwH1onPMIcd1pXTG0k5oQAJjMkTyLsEvYhl18hJJf6RBJJffKWDWJ bV00ah58VubFNjl43PkRg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfedvtddgjedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 16 Sep 2022 09:54:55 -0400 (EDT) Message-ID: Date: Fri, 16 Sep 2022 15:54:53 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: postgres_fdw hint messages Content-Language: en-US To: Nathan Bossart Cc: Tom Lane , Michael Paquier , Robert Haas , pgsql-hackers References: <1929340.1661531738@sss.pgh.pa.us> <20220901223128.GA932597@nathanxps13> <789102.1662073729@sss.pgh.pa.us> <20220901233120.GA934376@nathanxps13> <20220902212609.GA1216541@nathanxps13> <1267654.1662170814@sss.pgh.pa.us> <20220903043058.GA1264318@nathanxps13> <0fc339d4-3388-3849-4507-ef0fe0c783fa@enterprisedb.com> <20220913190255.GA2973985@nathanxps13> From: Peter Eisentraut In-Reply-To: <20220913190255.GA2973985@nathanxps13> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 13.09.22 21:02, Nathan Bossart wrote: > On Tue, Sep 13, 2022 at 08:32:43AM +0200, Peter Eisentraut wrote: >> I notice that for column misspellings, the hint is phrased "Perhaps you >> meant X." whereas here we have "Did you mean X?". Let's make that uniform. > > Good point. I attached a new version of the patch that uses the column > phrasing. I wasn't sure whether "reference" was the right word to use in > this context, but I used it for now for consistency with the column hints. > I think "specify" or "use" would work as well. I don't think we need a verb there at all. I committed it without a verb.