On Wed, Aug 28, 2013 at 2:04 PM, Robert Haas <robertmh...@gmail.com> wrote: >> Hm. Not this patches fault, but We seem to allow bgw_start_time == >> BgWorkerStart_PostmasterStart here which doesn't make sense... > > I can add a check for that. I agree that it's a separate patch.
On third thought, is there really any point to such a check? I mean, no background worker is going to start before it's registered, and by the time any background worker is registered, we'll be passed the time indicated by all of those constants: BgWorkerStart_PostmasterStart, BgWorkerStart_ConsistentState, BgWorkerStart_RecoveryFinished. I think we should view that field as fixing the earliest time at which the worker should be started, rather than the exact time at which it must be started. Otherwise no value is sensible. And if we take that approach, then for a dynamic background worker, any value is OK. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
