| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(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 21:55:19 |
| Message-ID: | 11936.1412373319@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-10-03 12:40:21 -0400, Bruce Momjian wrote:
>> Well, I think the issue is that having a GUC that can't reasonably be
>> tuned by 95% of our users is nearly useless. Few users are going to run
>> benchmarks to see what the optimal value is.
> It's possible to convince customers to play with a performance
> influencing parameter and see how the results are. Even in
> production.
I'm a bit dubious that people will be willing to experiment in production
with a GUC that requires a database restart to change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-10-03 21:58:14 | Re: Fixed xloginsert_locks for 9.4 |
| Previous Message | Andres Freund | 2014-10-03 21:48:52 | Re: pg_receivexlog and replication slots |