It seems EXECUTE SCRIPT is not working well together with log shipping.

Below there are the logs generated when I did "EXECUTE SCRIPT" adding a column
to a table.

Files 1 and 3 contain regular empty events (46575 and 46577), such as many generated by Slony-I
configured for log shipping, file 2 contains the ALTER statement from the script to be executed.

File 1 expects event counter to be at value 46574 and sets it to 46575. That is
what all other empty events do (increment counter by one). File 2 expects counter to
be at '46576' and sets it to '46576'. This file won't be executed, as, after applying 
file 1, the counter is at posision 46575. Applying file 3 will succeed (it expects 46575,
as set by file 1), but won't help, as the counter will be incremented to 46577. The counter
is never set to 46576, required by file 2, with the script to execute.

Greets,
        Jacek

#### File 1: slony1_log_1_00000000000000046575.sql

-- Slony-I log shipping archive
-- Node 1, Event 46575
start transaction;

select "_slony".setsyncTracking_offline(1, '46574', '46575', '2005-12-09 10:22:17.473521');
-- end of log archiving header
------------------------------------------------------------------
-- start of Slony-I data
------------------------------------------------------------------

------------------------------------------------------------------
-- End Of Archive Log
------------------------------------------------------------------
commit;
vacuum analyze "_slony".sl_setsync_offline;

#### File 2: slony1_log_1_00000000000000046576.sql

-- Slony-I log shipping archive
-- Node 1, Event 46576
start transaction;

select "_slony".setsyncTracking_offline(1, '46576', '46576', '2005-12-09 10:22:17.473521');
-- end of log archiving header
------------------------------------------------------------------
-- start of Slony-I data
------------------------------------------------------------------

ALTER TABLE int.devices ADD COLUMN device_hardware_type TEXT;


------------------------------------------------------------------
-- End Of Archive Log
------------------------------------------------------------------
commit;
vacuum analyze "_slony".sl_setsync_offline;


#### File 3: slony1_log_1_00000000000000046577.sql

-- Slony-I log shipping archive
-- Node 1, Event 46577
start transaction;

select "_slony".setsyncTracking_offline(1, '46575', '46577', '2005-12-09 10:22:46.701763');
-- end of log archiving header
------------------------------------------------------------------
-- start of Slony-I data
------------------------------------------------------------------

------------------------------------------------------------------
-- End Of Archive Log
------------------------------------------------------------------
commit;
vacuum analyze "_slony".sl_setsync_offline;