Re: Daniel Kahn Gillmor 2014-03-05 <[email protected]> > This would definitely require coordination from postgresql upstream, > though. i don't think the postgres binary supports this yet. it might
It certainly doesn't. > be worth raising to upstream at some point though. socket activation is > nice for at least three reasons: > 0) the process supervisor can hold the relevant sockets open so that no > other processes can grab them, even while the server in question is > being re-started). > > 1) for daemons that want to listen on reserved TCP or UDP ports (i.e. > below 1024), the process supervisor can open the ports, and then the > daemon itself can be run as a non-privileged user. > > 2) clients can establish a connection during a service restart, and > just have a delayed application-layer handshake, instead of getting > "port closed" messages. 3) auto-activation of services on connection. Though it might be difficult to get this (and 2) working with PostgreSQL because if you (re-)connect too early, you'll get "PostgreSQL is starting up" errors. Christoph -- [email protected] | http://www.df7cb.de/ _______________________________________________ Pkg-postgresql-public mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
