Re: proposal - function string_to_table

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: proposal - function string_to_table
Дата
Msg-id CAFj8pRC=2BdRYrqD88NSsbuMZxtgcugPW82v++ricrgauek+QA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: proposal - function string_to_table  (Peter Smith <smithpb2250@gmail.com>)
Ответы Re: proposal - function string_to_table  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers


út 25. 8. 2020 v 11:19 odesílatel Peter Smith <smithpb2250@gmail.com> napsal:
On Tue, Aug 25, 2020 at 4:58 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
> When you run ./unused_oids script, then you get this message
>
> [pavel@nemesis catalog]$ ./unused_oids
<snip>
> Patches should use a more-or-less consecutive range of OIDs.
> Best practice is to start with a random choice in the range 8000-9999.
> Suggested random unused OID: 8973 (1027 consecutive OID(s) available starting here)
>
> For me, this is simple protection against oid collision under development, and I expect so commiters does oid' space defragmentation.

I have not used that tool before. Thanks for teaching me!

:)


===

I have re-checked the string_to_table_20200825.patch.

Everything looks good to me now, so I am marking this as "ready for committer".

Thank you very much :)

Regard

Pavel


Kind Regards,
Peter Smith.
Fujitsu Australia

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

Предыдущее
От: Peter Smith
Дата:
Сообщение: Re: proposal - function string_to_table
Следующее
От: Anastasia Lubennikova
Дата:
Сообщение: [PATCH] Automatic HASH and LIST partition creation