Re: proposal - function string_to_table - Mailing list pgsql-hackers

From Peter Smith
Subject Re: proposal - function string_to_table
Date
Msg-id CAHut+Pvd2DoJ8d+YvyT-KL9-ss++0KMa4kh1stNdtmuD5=mMzA@mail.gmail.com
Whole thread Raw
In response to Re: proposal - function string_to_table  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal - function string_to_table  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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".


Kind Regards,
Peter Smith.
Fujitsu Australia



pgsql-hackers by date:

Previous
From: Jakub Wartak
Date:
Subject: Re: Handing off SLRU fsyncs to the checkpointer
Next
From: Pavel Stehule
Date:
Subject: Re: proposal - function string_to_table