Re: Avoiding smgrimmedsync() during nbtree index builds
От | Dmitry Dolgov |
---|---|
Тема | Re: Avoiding smgrimmedsync() during nbtree index builds |
Дата | |
Msg-id | 20220213143313.vhwg5ua6dcevbhlj@erthalion.local обсуждение исходный текст |
Ответ на | Re: Avoiding smgrimmedsync() during nbtree index builds (Melanie Plageman <melanieplageman@gmail.com>) |
Список | pgsql-hackers |
> On Wed, Feb 09, 2022 at 01:49:30PM -0500, Melanie Plageman wrote: > Hi, > v5 attached and all email feedback addressed below Thanks for the patch, it looks quite good. I don't see it in the discussion, so naturally curious -- why directmgr is not used for bloom index, e.g. in blbuildempty? > On Sun, Jan 16, 2022 at 3:26 PM Justin Pryzby <pryzby@telsasoft.com> wrote: > > Separate from this issue, I wonder if it'd be useful to write a DEBUG log > > showing when btree uses shared_buffers vs fsync. And a regression test which > > first SETs client_min_messages=debug to capture the debug log to demonstrate > > when/that new code path is being hit. I'm not sure if that would be good to > > merge, but it may be useful for now. I can't find the thread right away, but I vaguely remember a similar situation where such approach, as a main way to test the patch, had caused some disagreement. Of course for the development phase it would be indeed convenient.
В списке pgsql-hackers по дате отправления: