Re: Postgres 11 release notes

Поиск
Список
Период
Сортировка
От Amit Langote
Тема Re: Postgres 11 release notes
Дата
Msg-id 87cf0282-cee4-c651-0bb7-dbbc2bbfa75b@lab.ntt.co.jp
обсуждение исходный текст
Ответ на Re: Postgres 11 release notes  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: Postgres 11 release notes  (Bruce Momjian <bruce@momjian.us>)
Re: Postgres 11 release notes  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Список pgsql-hackers
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

Thanks,
Amit



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: overflow in snprintf() when printing INT64_MIN
Следующее
От: David Rowley
Дата:
Сообщение: Re: heap_sync seems rather oblivious to partitioned tables (wal_level=minimal)