Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dwaLY-0001hB-6y for pgsql-committers@arkaria.postgresql.org; Mon, 25 Sep 2017 20:51:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dwaLX-0005cp-Oh for pgsql-committers@arkaria.postgresql.org; Mon, 25 Sep 2017 20:51:19 +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 1dwaLI-0005C1-J6 for pgsql-committers@postgresql.org; Mon, 25 Sep 2017 20:51:04 +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 1dwaLA-0007K5-OP for pgsql-committers@postgresql.org; Mon, 25 Sep 2017 20:51:04 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2C1C721B97; Mon, 25 Sep 2017 16:50:54 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 25 Sep 2017 16:50:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=BlH3JJzo3fuFb5ueYyq8vtYw1JHr4sQ1s3cmEAUi5ZA=; b=faFRu8Nm v3TyTb2JTXAgUFDsef73I2rr8PUCsx25YdHt5Rdto/N9DVEpBV4Qw8TJK6yzRmJP nJJ1vkJmnLG0Gevgqc5PnC5W1zGjcNSwKro5PsGNUJ0nyGek0UpbpIN6J/kYVPw2 vKaJvWckA6iFn1zmvuNBxuOYPyTevMqRvgaMoy6WrLvBnT7AGNMJ3pTiTmsHdFba 1hvuV08CPxe96S3+ujrq4FxOQmaELj3EWDO9bfokXo/dz3FJiEmqYT9TW9Qb79ny jozFF520Qv2THdT/fzp1KPSwk5SJWHWT2/56Ui4l0Aq/Z3O4RNBTCWkAUWPIC6Qc OcMVsYm2tiMTVQ== X-ME-Sender: X-Sasl-enc: G3C/VVdLYqZGHK+A3xG2ryqv9W6Avg1CUlgS+UhUcWJn 1506372653 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 E5B0E2418B; Mon, 25 Sep 2017 16:50:53 -0400 (EDT) Subject: Re: pgsql: Give a better error for duplicate entries in VACUUM/ANALYZE colu To: Tom Lane References: <862733d5-f132-a59b-7afb-86002f946f80@2ndquadrant.com> <14181.1506366549@sss.pgh.pa.us> Cc: pgsql-committers@postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <7eb88e2f-a6c9-82b3-6add-7794cf6197e9@2ndquadrant.com> Date: Mon, 25 Sep 2017 16:50:53 -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: <14181.1506366549@sss.pgh.pa.us> 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-committers Precedence: bulk Sender: pgsql-committers-owner@postgresql.org On 9/25/17 15:09, Tom Lane wrote: > Peter Eisentraut writes: >> On 9/21/17 18:13, Tom Lane wrote: >>> Give a better error for duplicate entries in VACUUM/ANALYZE column list. > >> In the error message, we should write "specified more than once" instead >> of "specified twice", because that could otherwise look a bit silly: >> VACUUM ANALYZE vaccluster(i,i,i); >> ERROR: column "i" of relation "vaccluster" is specified twice > > OK. > >> (Also, the "is" doesn't seem to fit there.) > > Hm, reads fine to me, and I'd still rather include "is" in the > revised wording. Anybody else agree with Peter's wording? Note a big deal. I'm just working off existing error messages: msgid "parameter \"%s\" specified more than once" msgid "column name \"%s\" specified more than once" msgid "column \"%s\" specified more than once" msgid "filter variable \"%s\" specified more than once" msgid "option \"%s\" provided more than once" msgid "parameter name \"%s\" used more than once" msgid "storage type specified more than once" msgid "procedure number %d for (%s,%s) appears more than once" msgid "operator number %d for (%s,%s) appears more than once" msgid "publication name \"%s\" used more than once" msgid "relation \"%s\" would be inherited from more than once" msgid "column \"%s\" appears more than once in partition key" msgid "column name \"%s\" appears more than once in USING clause" msgid "common column name \"%s\" appears more than once in left table" msgid "common column name \"%s\" appears more than once in right table" msgid "WITH query name \"%s\" specified more than once" msgid "recursive reference to query \"%s\" must not appear more than once" msgid "XML attribute name \"%s\" appears more than once" msgid "argument name \"%s\" used more than once" msgid "table name \"%s\" specified more than once" -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers