Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
От | Pavel Borisov |
---|---|
Тема | Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. |
Дата | |
Msg-id | CALT9ZEFXK7Y3_5KefS8HtNRY5tzeRzOpj3fMd6SsAnTJTXaf9A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. (Alexander Korotkov <aekorotkov@gmail.com>) |
Ответы |
Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
|
Список | pgsql-hackers |
Hi, Alexander! On Wed, 25 Oct 2023 at 00:13, Alexander Korotkov <aekorotkov@gmail.com> wrote: > > On Wed, Sep 28, 2022 at 11:44 AM Aleksander Alekseev > <aleksander@timescale.com> wrote: > > > I think, this patch was marked as "Waiting on Author", probably, by mistake. Since recent changes were done withoutany 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 It's very good that this long-standing patch is finally committed. Thanks a lot! Regards, Pavel Borisov
В списке pgsql-hackers по дате отправления: