I've got slony (1.0.1) modified to run on PostgreSQL 7.2, and corrected
the LOG cursor to use an index (same plan as 7.3 and later).

The FETCH 100 FROM LOG; statement seems to take about 10 to 15 minutes,
gets run about 10 times, then a new cursor is defined and repeats.

Right now it's behind by about 50M tuples in log_1.

It appears it scans the entire table (of 50M entries) in order to find
the 1000 or so it wants for the current SYNC.

Is there a way to get it to catch up?

-- 
Rod Taylor <pg [at] rbt [dot] ca>

Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL