On Mon, Nov 25, 2024 at 7:06 PM Nazir Bilal Yavuz <byavu...@gmail.com> wrote: > > Hi, > > On Mon, 25 Nov 2024 at 16:19, Ashutosh Bapat > <ashutosh.bapat....@gmail.com> wrote: > > > > On Mon, Nov 25, 2024 at 6:47 PM Ashutosh Bapat > > <ashutosh.bapat....@gmail.com> wrote: > > > > > > > > For patch 2, it will be good to introduce expanded functionality to > > > make as well. But patch 1 is ready for the committer. So marked > > > accordingly. > > > > > > > Didn't find a CF entry for this. Please create and update. > > It is added and marked as ready for the committer [1]. There are > multiple 'Jian He' users in the commitfest app, so I couldn't add you > as a reviewer; please add yourself. > > [1] https://commitfest.postgresql.org/51/5405/
In order to debug a failure in SQL/PGQ patch, I needed to run regression test with some instrumentation which caused the regression run to take more than 1000 seconds. The failure is seen only in one of the tests. Spending 1000 seconds to reproduce or test patch just for one test seems too expensive. If we commit this patch, we could instead run check-tests equivalent in meson to save time and resources. The patch is ready for a committer already. -- Best Wishes, Ashutosh Bapat
