Re: Postgres 11 release notes - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: Postgres 11 release notes
Date
Msg-id 1f5b2e66-7ba8-98ec-c06a-aee9ff33f050@postgresql.org
Whole thread Raw
In response to Re: Postgres 11 release notes  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Postgres 11 release notes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 9/27/18 9:21 PM, Amit Langote wrote:
> 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:
>>>
>>> +       <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".
>
> 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

Sorry for the slow turnaround on this. Excellent suggestion. I have
updated the patches, please see attached.

Thanks,

Jonathan

Attachment

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: WIP: Avoid creation of the free space map for small tables
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: Segfault when creating partition with a primary key and sql_droptrigger exists