Re: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls
От | Alvaro Herrera |
---|---|
Тема | Re: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |
Дата | |
Msg-id | 20130930160818.GC5235@eldon.alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Re: Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls (Nicholas White <n.j.white@gmail.com>) |
Ответы |
Re: Re: Request for Patch Feedback: Lag & Lead Window
Functions Can Ignore Nulls
|
Список | pgsql-hackers |
Nicholas White escribió: > > But even if we did decide to switch memory contexts on every call, it would still be much cleaner than this. > > I've removed all the bms_initalize code from the patch and am using > this solution. As the partition memory is zero-initialised I just > store a Bitmapset pointer in the WinGetPartitionLocalMemory. The > bms_add_member and bms_is_member functions behave sensibly for > null-pointer inputs (they return a bms_make_singleton in the current > memory context and false respectively). I've surrounded the calls to > bms_make_singleton with a memory context switch (to the partition's > context) so the Bitmapset stays in the partition's context. Now that I look again, would GetMemoryChunkContext() be useful here? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: