| From: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Installed. Now what? |
| Date: | 2011-11-20 10:28:34 |
| Message-ID: | CAFWfU=tttefW7zNS6drg2+=wRm6yybdmfob3ZbXhE5M4cmN3pA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Nov 20, 2011 at 4:49 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 11/19/11 11:42 PM, Phoenix Kiula wrote:
>
> does this firewall block localhost at all? many don't. (I'm not at all
> familiar with this CSF/LFD thing)
>
> if you enable a port for TCP_IN, does it automatically allow replies back?
>
> postgres uses no UDP.
The firewall is set to:
1. Ignore the process pgbouncer (in fact the entire directory in which
pgbouncer sits)
2. Allow 127.0.0.1 for everything, no limitations
3. Yes, it can allow replies back (the same settings work with
postgresql, should pgbouncer be any different?)
I tried disabling the firewall completely. Same thing -- pgbouncer
still does not work.
It's not the firewall. It isn't blocking anything. Nothing in the logs
related to pgbouncer. I merely mentioned it as a step.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2011-11-20 10:32:42 | Adding 1 week to a timestamp, which can be NULL or expired |
| Previous Message | hubert depesz lubaczewski | 2011-11-20 10:19:15 | Re: invalid byte sequence for encoding "UTF8": 0x00 |