Re: [HACKERS] Setting pd_lower in GIN metapage
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] Setting pd_lower in GIN metapage |
Дата | |
Msg-id | CAB7nPqQ0wA=iE1mpXq6DZB93UKqKg41xZB18Sn9OADHfL6g4dw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Setting pd_lower in GIN metapage (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On Wed, Sep 20, 2017 at 12:49 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: > On Wed, Sep 20, 2017 at 4:25 AM, Michael Paquier > <michael.paquier@gmail.com> wrote: >> Also, _hash_init() would need some extra work to >> generate FPWs, but I don't think that it is necessary per its handling >> of a per-record meta data either. So REGBUF_STANDARD could be just >> removed from there, and there is actually no need to patch >> src/backend/access/hash at all. >> > > I think there is no need to remove it. As per discussion above, we > want to keep REGBUF_STANDARD for all metapage initializations for the > matter of consistency and that will be useful for > wal_consistency_checking in which case we anyway need full page image. Arf, yes. You are indeed right. I misread that you still need that anyway in XLogRecordAssemble. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: