On 23/09/10 12:32, Dimitri Fontaine wrote:
Heikki Linnakangas<heikki.linnakan...@enterprisedb.com> writes:
Hmm, that situation can arise if there's a network glitch which leads the
standby to disconnect, but the master still considers the connection as
alive. When the standby reconnects, the master will see two simultaneous
connections from the same standby. In that scenario, you clearly want to
disconnect the old connetion in favor of the new one. Is there a scenario
where you'd want to keep the old connection instead and refuse the new
one?
Protection against spoofing? If connecting with the right IP is all it takes…
You also need to authenticate with a valid username and password, of
course. As the patch stands, that needs to be a superuser, but we should
aim for smarter authorization than that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
