Re: [HACKERS] increasing the default WAL segment size
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] increasing the default WAL segment size |
Дата | |
Msg-id | CA+TgmobRWrVDUaHf1YbYxN-LYT1JD36Pw4=K_Zz4PeavNfEukw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] increasing the default WAL segment size (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] increasing the default WAL segment size
|
Список | pgsql-hackers |
On Wed, Jan 4, 2017 at 9:47 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > On 4 January 2017 at 13:57, Robert Haas <robertmhaas@gmail.com> wrote: >> On Wed, Jan 4, 2017 at 3:05 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >>> Strange response. Nothing has been assumed. I asked for tests and you >>> provided measurements. >> >> Sure, of zero-filling a file with dd. But I also pointed out that in >> a real PostgreSQL cluster, the change could actually *reduce* latency. > > I think we are talking at cross purposes. We agree that the main > change is useful, but it causes another problem which I can't see how > you can characterize as reduced latency, based upon your own > measurements. Zero-filling files will take longer if the files are bigger. That will increase latency. But we will also have fewer forced end-of-segment syncs. That will reduce latency. Which effect is bigger? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: