Date: Thu, 27 Sep 2018 11:24:07 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
	Bruce Momjian <bruce@momjian.us>,
	Michael Banck <michael.banck@credativ.de>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Postgres 11 release notes
Message-ID: <20180927142407.uco4e7s5qciqrhnu@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <e1d41e36-d08b-d1aa-93b4-3ff5b0456992@lab.ntt.co.jp>
User-Agent: NeoMutt/20180716
Precedence: bulk

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:
> 
> +       <listitem>
> +        <para>
> +         Having a "default" partition for storing data that does not match a
> +         partition key
> +        </para>
> +       </listitem>
> 
> 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".

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services