Hello,
> As discussed in [1], we're taking this opportunity to return some patchsets
> that don't appear to be getting enough reviewer interest.
Thank you for your helpful comments.
As you say, my patch doesn't seem to be of much interest to reviewers either.
I will discard the patch I proposed this time and consider it again.
Regards,
Noriyoshi Shinoda
-----Original Message-----
From: Jacob Champion <jchamp...@timescale.com>
Sent: Tuesday, August 2, 2022 5:45 AM
To: Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi.shin...@hpe.com>; Masahiko
Sawada <sawada.m...@gmail.com>; Fujii Masao <masao.fu...@oss.nttdata.com>
Cc: Justin Pryzby <pry...@telsasoft.com>; PostgreSQL-development
<pgsql-hack...@postgresql.org>; Julien Rouhaud <rjuju...@gmail.com>; Tom Lane
<t...@sss.pgh.pa.us>; Kyotaro Horiguchi <horikyota....@gmail.com>
Subject: Re: Improve logging when using Huge Pages
As discussed in [1], we're taking this opportunity to return some patchsets
that don't appear to be getting enough reviewer interest.
This is not a rejection, since we don't necessarily think there's anything
unacceptable about the entry, but it differs from a standard "Returned with
Feedback" in that there's probably not much actionable feedback at all. Rather
than code changes, what this patch needs is more community interest. You might
- ask people for help with your approach,
- see if there are similar patches that your code could supplement,
- get interested parties to agree to review your patch in a CF, or
- possibly present the functionality in a way that's easier to review
overall.
(Doing these things is no guarantee that there will be interest, but it's
hopefully better than endlessly rebasing a patchset that is not receiving any
feedback from the community.)
Once you think you've built up some community support and the patchset is ready
for review, you (or any interested party) can resurrect the patch entry by
visiting
https://commitfest.postgresql.org/38/3310/
and changing the status to "Needs Review", and then changing the status again
to "Move to next CF". (Don't forget the second step; hopefully we will have
streamlined this in the near future!)
Thanks,
--Jacob
[1] https://postgr.es/m/86140760-8ba5-6f3a-3e6e-5ca6c060b...@timescale.com
