Re: PATCH: Using BRIN indexes for sorted output
От | vignesh C |
---|---|
Тема | Re: PATCH: Using BRIN indexes for sorted output |
Дата | |
Msg-id | CALDaNm2PisBnPGuL-VvSjEf8UqN4frydX5HOB7siDoxc9M0+yQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: PATCH: Using BRIN indexes for sorted output (vignesh C <vignesh21@gmail.com>) |
Список | pgsql-hackers |
On Sun, 21 Jan 2024 at 07:32, vignesh C <vignesh21@gmail.com> wrote: > > On Wed, 2 Aug 2023 at 21:34, Tomas Vondra <tomas.vondra@enterprisedb.com> wrote: > > > > > > > > On 8/2/23 17:25, Sergey Dudoladov wrote: > > > Hello, > > > > > >> Parallel version is not supported, but I think it should be possible. > > > > > > @Tomas are you working on this ? If not, I would like to give it a try. > > > > > > > Feel free to try. Just keep it in a separate part/patch, to make it > > easier to combine the work later. > > > > >> static void > > >> AssertCheckRanges(BrinSortState *node) > > >> { > > >> #ifdef USE_ASSERT_CHECKING > > >> > > >> #endif > > >> } > > > > > > I guess it should not be empty at the ongoing development stage. > > > > > > Attached a small modification of the patch with a draft of the docs. > > > > > > > Thanks. FWIW it's generally better to always post the whole patch > > series, otherwise the cfbot gets confused as it's unable to combine > > stuff from different messages. > > Are we planning to take this patch forward? It has been nearly 5 > months since the last discussion on this. If the interest has gone > down and if there are no plans to handle this I'm thinking of > returning this commitfest entry in this commitfest and can be opened > when there is more interest. Since the author or no one else showed interest in taking it forward and the patch had no activity for more than 5 months, I have changed the status to RWF. Feel free to add a new CF entry when someone is planning to resume work more actively by starting off with a rebased version. Regards, Vignesh
В списке pgsql-hackers по дате отправления: