From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Replication timeout units |
Date: | 2012-08-26 03:02:07 |
Message-ID: | 20120826030207.GJ10814@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 20, 2011 at 11:34:25AM -0600, Kevin Grittner wrote:
> Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> > Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> >> from postgresql.conf.sample:
> >>
> >> #replication_timeout = 60s # in milliseconds; 0 disables
> >>
> >> Seconds or milliseconds? I would suggest we just remove the "in
> >> milliseconds", and instead say "timeout for replication
> >> connections; 0 disables".
> >
> > +1 from me. That's very confusing.
>
> Isn't it providing information on both the granularity and the
> default unit if none is specified? Why is it more confusing here
> than statement_timeout or any of the other places this pattern is
> followed?
>
> -1 from me on removing it *only* here.
FYI, I looked into this and can't see a way to improve it.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-08-26 03:26:11 | Re: Standalone synchronous master |
Previous Message | Bruce Momjian | 2012-08-26 02:59:00 | Re: psql output locations |