http://www.slony.info/bugzilla/show_bug.cgi?id=181

--- Comment #4 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-01-17 08:31:58 PST ---
In trying to run the regression test, I'm running into some problems with the
"search-for-highest-ID" functions.

When the regression test script tries to add the tables in, node #2 hasn't yet
been initialized, and so the function slonik_get_next_tab_id() fails.


-----------------------------------------------------
-> % cat /tmp/slony-regress.DbP0kt/slonik.script
include </tmp/slony-regress.DbP0kt/slonik.preamble>;
init cluster (id=1, comment = 'Regress test node');
echo 'update functions on node 1 after initializing it';
update functions (id=1);
create set (id=1, origin=1, comment='All test1 tables');

set add table (set id = 1, tables='public.*');
-----------------------------------------------------

-> % cat /tmp/slony-regress.DbP0kt/slonik.log
<stdin>:4: WARNING:  This node is running PostgreSQL 8.3 - cannot apply
TRUNCATE triggers
CONTEXT:  SQL statement "SELECT "_slony_regress1".add_truncate_triggers()"
PL/pgSQL function "upgradeschema" line 12 at PERFORM
<stdin>:7: PGRES_FATAL_ERROR select max(tab_id) FROM "_slony_regress1".sl_table
- ERROR:  schema "_slony_regress1" does not exist
LINE 1: select max(tab_id) FROM "_slony_regress1".sl_table
                                ^
<stdin>:2: Possible unsupported PostgreSQL version (90100) 9.1, defaulting to
8.4 support
<stdin>:3: update functions on node 1 after initializing it
<stdin>:4: Possible unsupported PostgreSQL version (90100) 9.1, defaulting to
8.3 support
<stdin>:7: Error: could not query node 2 for next table id

I think we need to treat nodes that aren't accessible as not being a cause for
failure, but rather a cause for ignoring them.

The same almost certainly applies to slonik_get_next_sequence_id()

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.