Jaime Casanova jcasanov at systemguards.com.ec
Wed Apr 21 21:14:44 PDT 2010
On Wed, Apr 21, 2010 at 6:52 PM, Jan Wieck <JanWieck at yahoo.com> wrote:
> On 4/21/2010 7:44 PM, Jaime Casanova wrote:
>>
>> On Wed, Apr 21, 2010 at 6:24 PM, Jan Wieck <JanWieck at yahoo.com> wrote:
>>>
>>> On 4/21/2010 7:06 PM, Jaime Casanova wrote:
>>>>
>>>>
>>>> any ideas on what look for the sl_log_x problem?
>>>
>>> What does sl_status look like on the origin?
>>>
>>>
>>
>> mic=# select * from _sncp_incop_cluster.sl_status ;
>> -[ RECORD 1 ]---------------+---------------------------
>> st_origin                         | 1
>> st_received                     | 2
>> st_last_event                  | 843427
>> st_last_event_ts              | 2010-04-21 18:42:18.671167
>> st_last_received              | 786330
>> st_last_received_ts          | 2010-04-20 16:04:58.747498
>> st_last_received_event_ts | 2010-04-20 02:26:44.601898
>> st_lag_num_events          | 57097
>> st_lag_time                     | 1 day 16:15:35.203507
>>
>
> So who did the manual delete from sl_event on node 2?
>

no one i'm aware of, i looked in .psql_history and doesn't find
anything about sl_event either.
what i remember i did (and sorry for no remember this before, don't
know if it's important) was that the first time the subscribe didn't
work it first says that the table didn't exist... and that was because
the oid of the table in tab_reloid in node 2 was wrong (the oid didn't
exist, i guess it was the oid of the table before i drop it and
recreated it with the missing field) so i... ehhh... updated
sl_table.tab_reloid to the right oid...

so the steps were something like:
- in node 1
   - slonik set drop table in node1
   - rename table, create a new one, migrate and drop old table

in node 2
   - drop table, recreate it using pg_dump -t -h ip_origin

in node 1
   - slonik create set
   - slonik set add table
   - slonik subscribe set

error

in node 1
   - slonik unsubscribe set

in node 2
   - update bad oid

when i try to subscribe again, there was the error about the table
already existing in sl_table (which i know isn't true)

-- 
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157


More information about the Slony1-general mailing list