| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Standby registration |
| Date: | 2010-09-23 09:34:51 |
| Message-ID: | 4C9B1F3B.1070205@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23/09/10 12:32, Dimitri Fontaine wrote:
> Heikki Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-09-23 09:35:47 | Re: wip: functions median and percentile |
| Previous Message | Dimitri Fontaine | 2010-09-23 09:32:07 | Re: Standby registration |