tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
in [PgSql]
|
Prev: [HACKERS] tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)
Next: commented out para in docs
From: Heikki Linnakangas on 22 Feb 2010 13:50 Jaime Casanova wrote: > > if we can do this, how should it work? > Simon said: > """ > Yes, I think so. Rough design... > > integrated_user_processes = 'x, y, z' > > would run x(), y() and z() in their own processes. These would execute > after startup, or at consistent point in recovery. The code for these > would come from preload_libraries etc. > > They would not block smart shutdown, though their shudown sequence might > delay it. User code would be executed last at startup and first thing at > shutdown. > > API would be user_process_startup(), user_process_shutdown(). > """ > > so it should be a GUC, that is settable only at start time. A GUC like that was my first thought too. We've already come up with many uses for it, so whatever the interface is, will need to make sure it's flexible enough to cater for all the use cases. > we need those integrated processes at all when in a standby server? Yes. You might want to run e.g. scheduled reports from a standby reporting server, launched by a scheduler process. Or backups. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |