> 2021年1月7日 22:16，Bruce Momjian <bruce@momjian.us> 写道：
>
> On Thu, Jan 7, 2021 at 05:44:01PM +0800, 曾文旌 wrote:
>> I've been following this topic for a long time. It's been a year since the last response.
>> It was clear that our customers wanted this feature as well, and a large number of them mentioned it.
>>
>> So, I wish the whole feature to mature as soon as possible.
>> I summarized the scheme mentioned in the email and completed the POC patch(base on PG_13).
>
> I think you need to address the items mentioned in this blog, and the
> email link it mentions:
>
> https://momjian.us/main/blogs/pgblog/2020.html#July_1_2020
Thank you for your reply.
I read your blog and it helped me a lot.
The blog mentions a specific problem: "A large global index might also reintroduce problems that prompted the creation
ofpartitioning in the first place. "
I don't quite understand, could you give some specific information?
In addition you mentioned: "It is still unclear if these use-cases justify the architectural changes needed to enable
globalindexes."
Please also describe the problems you see, I will confirm each specific issue one by one.
Thanks
Wenjing
>
> I am not clear this is a feature we will want. Yes, people ask for it,
> but if the experience will be bad for them and they will regret using
> it, I am not sure we want it. Of course, if you code it up and we get
> a good user experience, we would want it --- I am just saying it is not
> clear right now.
>
> --
> Bruce Momjian <bruce@momjian.us> https://momjian.us
> EnterpriseDB https://enterprisedb.com
>
> The usefulness of a cup is in its emptiness, Bruce Lee
