Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmObh-0005Nh-Qq for pgsql-docs@arkaria.postgresql.org; Tue, 20 Sep 2016 17:13:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bmObh-00028H-DW for pgsql-docs@arkaria.postgresql.org; Tue, 20 Sep 2016 17:13:21 +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 1bmObL-0001GP-1O for pgsql-docs@postgresql.org; Tue, 20 Sep 2016 17:12:59 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bmObH-0003bC-UB for pgsql-docs@postgresql.org; Tue, 20 Sep 2016 17:12:58 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 1052C205B7; Tue, 20 Sep 2016 13:12:54 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 20 Sep 2016 13:12:54 -0400 DKIM-Signature: v=1; a=rsa-sha1; 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-sasl-enc:x-sasl-enc; s=smtpout; bh=flXzwwZMt9xNwEk iYDndLeYIEzA=; b=RQEGMqLgdLvlgMpdpyPTOiZbB+TBRLB4Q7Ac/PmHttxVvK8 HrygUnRgmXyAGS2WHzCKWPw+KK6pjd3o1YRLUIjZmDzIUaEuskSYI8gOwg9A4ASe nKgHFgTJ5w3D0jvP/vHHGETujABLROrPR1opuRD3eJF6GJsR4rCuP0gVaFcI= X-Sasl-enc: p4ftyJz/JOrGPPqmCtMjPlS7AbWisxjXY9Me1CxBWhZE 1474391573 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 BDC74CCE8B; Tue, 20 Sep 2016 13:12:53 -0400 (EDT) Subject: Re: update to alter user mapping example To: gabrielle , pgsql-docs@postgresql.org References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <4cd43ca8-d66d-1811-e51f-3c6780d91e21@2ndquadrant.com> Date: Tue, 20 Sep 2016 13:12:53 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 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 8/24/16 9:07 PM, gabrielle wrote: > The example for ALTER USER MAPPING is missing the action keyword > (ADD|SET|DROP). > > Since ADD is the default option, the given command attempts to add a > user 'bob' to the already-existing user mapping 'bob', which throws an > 'ERROR: option "user" provided more than once' > > Here's a working example that a) matches the description ("change > password") and b) continues the steps started with the CREATE USER > MAPPING example. > > ALTER USER MAPPING FOR bob SERVER foo OPTIONS (SET password 'public'); > > I've attached a patch as well. Fixed, thanks. -- 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