Hi,
Quick question, are there any more revisions left to be done on this patch from
the previous feedback?
Or should I continue with reviewing the current patch?
Regards,
Akshat Jaimini
ription for
a patch explaining its history and need in brief would be really helpful
for people to get started instead of trying to make sense of a very large
email thread. This is a small addition but it would definitely make it
easier for new reviewers and contributors.
Regards,
Akshat Jaimin
Hi apologies for the late reply.
> Maybe you forgot to recompile/reinstall after updating past that commit?
I did recompile it earlier but just to be sure I followed the steps again
and now its working!
Regards,
Akshat Jaimini
On Wed, Apr 3, 2024 at 12:34 AM Tom Lane wrote:
> Akshat J
reviews.
Changing the status to 'Ready for Committer'.
Regards,
Akshat Jaimini
The new status of this patch is: Ready for Committer
Hii,
I am currently trying to review the submitted patch but I am not able to apply
it to the master branch.
Regards,
Akshat Jaimini
I think we should move this patch to the next CF as I believe that work is
still going on resolving the last reported bug.
Hello!
I was going through the previous conversations for this particular patch and it
seems that this patch failed some tests previously?
Imo we should move it to the next CF so that the remaining issues can be
resolved accordingly.
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: tested, passed
Documentation:not tested
Passes the default cases; Does not make any trivial changes to th
The patch looks fine and passes all the tests. I am using Arch Linux on an
x86_64 system.
The patch does not cause any unnecessary bugs and does not make any non trivial
changes to the source code.
I believe it is ready to be committed!
The new status of this patch is: Ready for Committer