Hi all:
Two months have passed by now, and I'm wondering if the issue mentioned in [1] has been resolved yet?
Returning to this question, does anyone have any new opinions on it? If not, should we consider fixing this problem?
Or is this considered a bug that's not worth fixing?
[1] https://www.postgresql.org/message-id/29273AF3-9684-4069-9257-D05090B03B99@amazon.com
Best Regards,
Haiyang Li