On Wed, Sep 28, 2022 at 11:44 AM Aleksander Alekseev <aleksan...@timescale.com> wrote: > > I think, this patch was marked as "Waiting on Author", probably, by > > mistake. Since recent changes were done without any significant code > > changes and CF bot how happy again. > > > > I'm going to move it to RfC, could I? If not, please tell why. > > I restored the "Ready for Committer" state. I don't think it's a good > practice to change the state every time the patch has a slight > conflict or something. This is not helpful at all. Such things happen > quite regularly and typically are fixed in a couple of days.
This patch seems useful to me. I went through the thread, it seems that all the critics are addressed. I've rebased this patch. Also, I've run perltidy for tests, split long errmsg() into errmsg(), errdetail() and errhint(), and do other minor enchantments. I think this patch is ready to go. I'm going to push it if there are no objections. ------ Regards, Alexander Korotkov
0001-Teach-contrib-amcheck-to-check-the-unique-constr-v18.patch
Description: Binary data
