Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bV1c7-0007SJ-Vr for pgsql-docs@arkaria.postgresql.org; Wed, 03 Aug 2016 19:14:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bV1c7-00075s-5B for pgsql-docs@arkaria.postgresql.org; Wed, 03 Aug 2016 19:13:59 +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 1bV1c6-00074O-Fj for pgsql-docs@postgresql.org; Wed, 03 Aug 2016 19:13:58 +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 1bV1c3-0001vC-5Q for pgsql-docs@postgresql.org; Wed, 03 Aug 2016 19:13:58 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id C142F20345; Wed, 3 Aug 2016 15:13:53 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 03 Aug 2016 15:13:53 -0400 DKIM-Signature: v=1; a=rsa-sha1; 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-sasl-enc:x-sasl-enc; s=smtpout; bh=g74QuwQOyJ4POHV MCrDzwTG6Pb4=; b=kOlYzsyvVXb7f5R+VI6o6hTT7qCiCSzH7vBwdfnpU+5TVlQ F1KBnGOkM6agTCcCq9Syyqcv4jBnuI5DvOAhB7tS9WLqMLHzq5mBPiPvPfsLXSNG gGv19twBI1mTrce3Iiuo1mv5gEVL0goU/NOBukdf+itrmFXnJ6985tlOGvEU= X-Sasl-enc: aFcnnNW6rvp9Sp628suvRH2e+VQJEdVCGK8dK2MtjGr9 1470251633 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 82DACF2D29; Wed, 3 Aug 2016 15:13:53 -0400 (EDT) Subject: Re: Might be worth mentioning that temp_tablespaces can contain duplicate values To: pgsql-docs@postgresql.org References: <20160706014353.1409.66495@wrigleys.postgresql.org> Cc: alecz@berkeley.edu From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 3 Aug 2016 15:13:53 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160706014353.1409.66495@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 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 7/5/16 9:43 PM, alecz@berkeley.edu wrote: > Page: https://www.postgresql.org/docs/9.5/static/runtime-config-client.html > Description: > > The section on temp_tablespaces is here: > https://www.postgresql.org/docs/9.5/static/runtime-config-client.html > > I've tried setting temp_tablespaces with duplicate entries and have found > that it keeps those duplicates, making that entry used more frequently. This > is useful if the user wants to use one tablespace more frequently than > others. Example: "tablespace1, tablespace1, tablespace2" It'll pick > tablespace1 about 2X as often as tablespace2. > > Support for duplicate values isn't explicitly mentioned in the > documentation, but I inferred it from the wording about the parameter being > a "list." But I had to go test to make sure it would work as I thought. Anyone have concerns about explicitly documenting this behavior? Seems possibly useful to me. -- 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