| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should commit_delay be PGC_SIGHUP? |
| Date: | 2013-03-22 12:47:14 |
| Message-ID: | CAM3SWZQ+RVikQ2Nwt+WKKneqxaJ8X3zK3ND+-6MS1Gu4qDh5JA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 22, 2013 at 12:42 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> This is fine with me, too, and I agree that it's warranted... but your
> commit message supposes that this behavior is new in 9.3, and I think
> it dates to 9.2.
No, it doesn't. It just missed the deadline for 9.2.
I'm happy enough to have the setting be PGC_SUSET, since that more or
less conveys that commit_delay isn't something that is sensible to set
dynamically.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-03-22 13:29:59 | Re: JSON Function Bike Shedding |
| Previous Message | Ants Aasma | 2013-03-22 12:45:58 | Re: Page replacement algorithm in buffer cache |