Re: WAL usage calculation patch
От | Julien Rouhaud |
---|---|
Тема | Re: WAL usage calculation patch |
Дата | |
Msg-id | CAOBaU_ZBHCmAAZRV2sOveVdRqFiSXkjHuaEdZ+Kgn=q_XJRFtQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: WAL usage calculation patch (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: WAL usage calculation patch
|
Список | pgsql-hackers |
On Mon, Apr 27, 2020 at 8:12 AM Michael Paquier <michael@paquier.xyz> wrote: > > On Mon, Apr 27, 2020 at 08:35:51AM +0530, Amit Kapila wrote: > > On Thu, Apr 23, 2020 at 2:35 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > >> On Thu, Apr 23, 2020 at 12:16 PM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > >>> The internal symbol for the WAL record is > >>> XLOG_FPI and xlogdesc.c prints it as "FPI". > > > > Julien, Peter, others do you have any opinion here? I think it is > > better if we decide on one of FPW or FPI and make the changes at all > > places for this patch. > > It seems to me that Peter is right here. A full-page write is the > action to write a full-page image, so if you consider only a way to > define the static data of a full-page and/or a quantity associated to > it, we should talk about full-page images. I agree with that definition. I can send a cleanup patch if there's no objection.
В списке pgsql-hackers по дате отправления: