Re: WAL usage calculation patch
От | Amit Kapila |
---|---|
Тема | Re: WAL usage calculation patch |
Дата | |
Msg-id | CAA4eK1+Gwy=-teh7dGYY03qsYVAekHfokie8LWSwGXOGp3YOMw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: WAL usage calculation patch (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: WAL usage calculation patch
|
Список | pgsql-hackers |
On Mon, Apr 6, 2020 at 10:01 PM Justin Pryzby <pryzby@telsasoft.com> wrote: > > On Mon, Apr 06, 2020 at 05:01:30PM +0200, Peter Eisentraut wrote: > > I noticed in some of the screenshots that were tweeted that for example in > > > > WAL: records=1 bytes=56 > > > > there are two spaces between pieces of data. This doesn't match the rest of > > the EXPLAIN output. Can that be adjusted? > > We talked about that here: > https://www.postgresql.org/message-id/20200402054120.GC14618%40telsasoft.com > Yeah. Just to brief here, the main reason was that one of the fields (full page writes) already had a single space and then we had prior cases as mentioned in Justin's email [1] where we use two spaces which lead us to decide using two spaces in this case. Now, we can change back to one space as suggested by you but I am not sure if that is an improvement over what we have done. Let me know if you think otherwise. [1] - https://www.postgresql.org/message-id/20200402054120.GC14618%40telsasoft.com -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: