| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Smith <gregsmithpgsql(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fixed xloginsert_locks for 9.4 |
| Date: | 2014-10-03 22:16:28 |
| Message-ID: | 20141003221628.GM14522@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 4, 2014 at 12:13:00AM +0200, Andres Freund wrote:
> > Do we really want to expose a setting a few of us _might_ ask customers
> > to change?
>
> They also will try that themselves. Our customers aren't a horde of dumb
> people. Some of them are willing to try things if they hit scalability
> problesm. And *lots* of people hit scalability problems with
> postgres. In fact I've seen big users migrate away from postgres because
> of them.
>
> And it's not like this only affects absurd cases. Even a parallel
> restore will benefit.
I disagree. I just don't see the value in having such undefined
variables.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-10-03 22:21:23 | Re: Fixed xloginsert_locks for 9.4 |
| Previous Message | Andres Freund | 2014-10-03 22:13:00 | Re: Fixed xloginsert_locks for 9.4 |