Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g5hTh-0000AA-F5 for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Sep 2018 01:21:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g5hTd-0004e4-Aw for pgsql-hackers@arkaria.postgresql.org; Fri, 28 Sep 2018 01:21:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g5hTc-0004dx-W0 for pgsql-hackers@lists.postgresql.org; Fri, 28 Sep 2018 01:21:53 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g5hTX-0007Ej-JR; Fri, 28 Sep 2018 01:21:50 +0000 Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id w8S1LPsN016556; Fri, 28 Sep 2018 10:21:25 +0900 Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 40D49EA789B; Fri, 28 Sep 2018 10:21:25 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 36020EA7764; Fri, 28 Sep 2018 10:21:25 +0900 (JST) Received: from [127.0.0.1] (unknown [129.60.241.61]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 2E957400976; Fri, 28 Sep 2018 10:21:25 +0900 (JST) Subject: Re: Postgres 11 release notes References: <20180927142407.uco4e7s5qciqrhnu@alvherre.pgsql> From: Amit Langote Message-ID: <87cf0282-cee4-c651-0bb7-dbbc2bbfa75b@lab.ntt.co.jp> Date: Fri, 28 Sep 2018 10:21:16 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180927142407.uco4e7s5qciqrhnu@alvherre.pgsql> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: Alvaro Herrera Cc: "Jonathan S. Katz" , Bruce Momjian , Michael Banck , PostgreSQL-development X-TM-AS-MML: disable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2018/09/27 23:24, Alvaro Herrera wrote: > On 2018-Sep-27, Amit Langote wrote: > >> Sorry I couldn't reply sooner, but the following of your proposed text >> needs to be updated a bit: >> >> + >> + >> + Having a "default" partition for storing data that does not match a >> + partition key >> + >> + >> >> I think "does not match a partition key" is not accurate. Description of >> default partitions further below in the release notes says this: >> >> "The default partition can store rows that don't match any of the other >> defined partitions, and is searched accordingly." >> >> So, we could perhaps write it as: >> >> Having a "default" partition for storing data that does not match any of >> the remaining partitions > > Yeah, I agree that "a partition key" is not the right term to use there > (and that term is used in the press release text also). However I don't > think "remaining" is the right word there either, because it sounds as > if you're removing something. > > For the Spanish translation of the press release, we ended up using the > equivalent of "for the data that does not match any other partition". Yeah, "any other partition" is what the existing description uses too, so: Having a "default" partition for storing data that does not match any other partition Thanks, Amit