| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: increasing the default WAL segment size |
| Date: | 2016-08-25 15:01:40 |
| Message-ID: | CA+TgmoamPMsqO7siQsdr68bLEQDcGqWdanrdwNb1XsutwO2B2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 25, 2016 at 10:39 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Another issue is that many users are coming from database products that
> have significant performance hits in switching WAL files so they might
> be tempted to set very high segment sizes in inappropriate cases.
Well, we have some hit there, too. It may be smaller, but it's
certainly not zero.
I'm generally in favor of preventing people from setting ridiculous
values for settings; we shouldn't let somebody set the WAL segment
size to 8kB or something silly like that. But it's more important to
enable legitimate uses than it is to prohibit inappropriate uses. If
a particular value of a particular setting may be legitimately useful
to some users, we should allow it, even if some other user might
choose that value under false assumptions.
In short, let's eschew nannyism.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-08-25 15:04:06 | Re: increasing the default WAL segment size |
| Previous Message | Robert Haas | 2016-08-25 14:57:09 | Re: increasing the default WAL segment size |