Jeff Frost wrote:
>  
>>> and better yet, can you connect to both of them on the machine where the
>>> slons will run like this:
>>>
>>> psql -h au -p 5433 -U postgres my_db
>>> psql -h au -p 5432 -U postgres my_db
>>>
>>> and if so, what's the output of:
>>>
>>> select _my_db_cluster.getlocalnodeid('_my_db_cluster');
>>>
>>> on both those?
>> The first one (the master) reports 1, and the second one (the slave)
>> reports 2, as expected.
>>
>> So I guess the question is, why does slon think it is on the wrong node?
>> If it connects and does the getlocalnodeid() as you say, then what makes
>> it think that's the wrong node?  What tells it that node 2 is the wrong
>> one?
> 
> In that case, I bet one of the store paths is wrong.  I.e. it thinks it's
> connecting to node 1, but is really connecting to node 2.
> 
> Does the conninfo in _my_db_cluster.sl_path match the conninfo you expect to
> see?

On the master, something is odd:

my_db=# select * from _my_db_cluster.sl_path;
 pa_server | pa_client |            pa_conninfo               | pa_connretry 
-----------+-----------+--------------------------------------+--------------
         2 |         1 | dbname=my_db  host=au  user=postgres |           10
         1 |         2 | <event pending>                      |           10

Does that make any sense?

Craig