Re: Can we remove extra memset in BloomInitPage, GinInitPage and SpGistInitPage when we have it in PageInit?
От | Bharath Rupireddy |
---|---|
Тема | Re: Can we remove extra memset in BloomInitPage, GinInitPage and SpGistInitPage when we have it in PageInit? |
Дата | |
Msg-id | CALj2ACWOd9SWykgazp0NNyjy-R++m5=u=b3XWmaU547aTVNGiQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Can we remove extra memset in BloomInitPage, GinInitPage and SpGistInitPage when we have it in PageInit? (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Can we remove extra memset in BloomInitPage, GinInitPage and SpGistInitPage when we have it in PageInit?
Re: Can we remove extra memset in BloomInitPage, GinInitPage and SpGistInitPage when we have it in PageInit? |
Список | pgsql-hackers |
On Wed, Apr 7, 2021 at 11:44 AM Michael Paquier <michael@paquier.xyz> wrote: > > On Wed, Apr 07, 2021 at 06:31:19AM +0530, Bharath Rupireddy wrote: > > Setting p->pd_flags = 0; is unnecessary and redundant after memsetting > > the page to zeros. Also, see the existing code for pd_prune_xid, > > similarly I've done that for pd_flags. I think it's okay with /* > > p->pd_flags = 0; done by above MemSet */. > > Sure, but this one does not hurt much either as-is, so I have left it > out, and applied the rest. Thanks for pushing the patch. I wanted to comment out p->pd_flags = 0; in PageInit similar to the pd_prune_xid just for consistency. /* p->pd_prune_xid = InvalidTransactionId; done by above MemSet */ With Regards, Bharath Rupireddy. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: