| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication and postmaster signaling |
| Date: | 2010-01-06 08:28:06 |
| Message-ID: | 4B444996.105@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujii Masao wrote:
> On Tue, Jan 5, 2010 at 11:29 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>> This was probably discussed to death earlier, but: why was it decided to
>> not simply use a different port for listening for walsender
>> connections?
>
> I believe that using a different port would make the setup
> of replication messier; look for the unused port number,
> open that port for replication in the firewall, etc.
Actually, being able to firewall walsender traffic separately might be
rather handy.
Having to assign a different port wouldn't be fun for packagers, though,
especially those (like the Debian-derived Linux distros) who already try
to support more than one Pg version installed in parallel.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boszormenyi Zoltan | 2010-01-06 08:42:06 | Re: ecpg compile error |
| Previous Message | Boszormenyi Zoltan | 2010-01-06 08:11:39 | Re: ecpg compile error |